This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
When using the list format, the marker of list items are not displayed: e.g. <ol> <li>First</li> <li>Second</li> </ol> To display the marker, 'list-style-type' must be specified. It's unusable for project web site contents. <ol style="list-style-type: decimal"> See the test page for detail: http://nblocalizatoin.netbeans.org/docs/testfile.html
Sorry the correct URL for the test page is as follows: http://nblocalization.netbeans.org/docs/testfile.html
Petr will evaluate.
In base_packaged.css, the following declaration is guilty: ul,ol{list-style:none;}
*** Bug 177433 has been marked as a duplicate of this bug. ***
Thanks Jesse for evaluation. This asset is provided by kenai. Assigning to kenai team.
Do we have any idea when this will be fixed? This issue has a very big impact on all tutorials on platform.netbeans.org, which have steps and bulleted lists all over the place. Raising this to a P2.
Seems to be no movement whatsoever on this issue, meanwhile the NetBeans Platform is a P1 item for 6.8 while all its tutorials are broken because of this issue. As a result, I'm changing this issue to a P1.
Target milestone should definitely be 6.8.
removing the list-style:none property from: ul,ol{list-style:none;} will not fix this. It will end up breaking every other page besides those that want the list-style to be shown. It then just becomes another issue for those pages. The fix for this is not to mess with the base_packaged.css, but rather add a .css include to the top of the pages that need to override this behavior. It can be done in a couple of minutes by just adding one line and a file that has the following in it. ul,ol{list-style:disc;}
Why is this not necessary in all HTML files that are in "www"? E.g., this HTML file does not need an override, it just works correctly: http://netbeans.org/kb/trails/platform.html I am concerned that the suggestion seems to be a hack. Worse, an inconsistent hack, since we'll not be applying this hack to all our documentation.
Plus, the hack would need to be applied to, literally, thousands of pages...
The suggestion is a bit off in that is suggests adding another file. It should simply be a change to the existing nblnf.css file which is being used to override defaults as is for this project. The link that you are referring to, is using the netbeans.css file and not base_packaged.css and nblnf.css. The main www (Netbeans.org) site is using a separate PHP based navigation, while the sub-projects are using the navigation from Project Kenai itself. This is as requested. That is what causes the different css files to be used in the different parts of the site. Hope that explains things a little better. Sorry for the vague and incorrect first suggestion. --jb
So, the "nblnf.css" file needs to be changed. Who should this issue be reassigned to then? Please will the person who currently has this assigned to them assign it to whomever should be fixing that file.
(In reply to comment #13) The nblnf.css file is under the Kenai team control, from what I've just been told. It's already being worked on and all of this info has been worked out while working with the responsible engineer.
I find it bizarre that a standard CSS stylesheet would make list items not look like list items. The default should be that lists appear normally, without needing to include or override anything. If there are some pages in the site infrastructure which, for odd reasons, use lists that are not supposed to look like lists (<p> and <br> are not good enough?) then those pages should include a stylesheet which does that... or, better, the list-style=none rule should be enabled only based on some CSS criterion such as a class.
http://kenai.com/jira/browse/KENAI-1678 has been fixed. Normally this will go to production at the end of sprint on 12/14. Since this is urgent, let's see whether we can this bug verified on staging first, then we can see when it is a proper time to get deployed to production before 6.8 FCS.
Hi Keiichi, could you take a look on this link? http://nblocalization.testnetbeans.org/docs/testfile.html I copied there similar file to yours one for staging site, it seems to be all right there...
Hi Martin, I can't login to see that pointed URL: http://nblocalization.testnetbeans.org/docs/testfile.html Both my netbeans.org account and my kenai.com account does not work. Would you tell me how I can access that page?
Created attachment 92039 [details] screenshot Sorry I forgot that you mustn't have an access there. I created and attached screenshot.
I've confirmed screenshot. Thank you for your attaching. It seems that the fixing in that staging server is OK.
Since this was a showstopper for Netbeans.org. We deployed a hot fix to production earlier today. See http://nblocalization.netbeans.org/ for an example.
Thank you for your deployment! I've confirmed that the test file is now displayed without issues: http://nblocalization.netbeans.org/docs/testfile.html
Ok, the fix is on production site and it's working well. Verified.
Thank you very much! It all looks great.