Last modified: 2012-04-12 13:54:27 UTC
Created attachment 8680 [details] a = content = markup turns into a content border A heading named content is attributed with an id of "content", the CSS for which has a border, etc. = content = == content == === content === Temporary workarounds include = content = (tested) and adding #content to the Common.css probably (not tested) Thank you.
Problem: = content = produses an a tag with id="content" which is used by a layout div already. Solution: The skins' main.css files need be more precise using e.g. div#content instead of #content.
An HTML page should not have two of the same id attributes on one page, so CSS selector specificity is a good workaround but not a good fix. The bug produces two id="content" elements, apart from W3C non-conformance, nothing bad will happen unless one tries to traverse the DOM with two elements with asme id attributes. Trivial, slim chances of that ever happening.
The css uses div#content already in 1.17.0rc1.
*** This bug has been marked as a duplicate of bug 7356 ***
(In reply to comment #1) > Problem: = content = produses an a tag with id="content" which is used by a > layout div already. > > Solution: The skins' main.css files need be more precise using e.g. div#content > instead of #content. No need for an extra specific selector. #content is just fine, adding div in front of it adds more weight and could cause problems in other skins that are making assumptions on the cascading effects of CSS. (In reply to comment #2) > The bug produces > two id="content" elements, apart from W3C non-conformance, nothing bad will > happen unless one tries to traverse the DOM with two elements with asme id > attributes. Trivial, slim chances of that ever happening. Not trivial at all in my opinion. #content is one of the few elements that has a consistent ID in all skins, There are a huge amount of scripts referring to it through JavaScript DOM traversal.
