Closed Bug 553243 Opened 16 years ago Closed 15 years ago

Links dosn't shown/ work furthermore depending on Styledefinition

Categories

(Core :: CSS Parsing and Computation, defect)

All
Windows XP
defect
Not set
major

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: pas, Unassigned)

References

()

Details

(Keywords: css-moz, regression)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.2) Gecko/20100115 Firefox/3.6 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.2) Gecko/20100115 Firefox/3.6 since Firefox 3.6/ 3.7a4pre doesn’t work the links behind our tab elements within the websites furthermore (Ex. see: http://www.festo.com/cms/de_de/2384.htm or http://www.festo.com/cms/de_de/628.htm). We have try to analyse our CSS Files from the website. However it’s not possible to reproduce this failure with a simple CSS Statement. We found 2 possibilities, which have an influence to this behavior. What we know, if we change the value of the css statement "display" or if we remove the value after in the section ".clearfix: after" within our initial.css .clearfix:after { content: "."; display: block; height: 0; clear: both; font-size: 1px; visibility: hidden; } or in the second css File "content.css" Section 7 display: inline; div.tab-cards ul.tabs { display:inline; position: relative; top:2px; z-index: 2; } the links on the tabs runs well again. However the rest of the site looks than bad. I don’t know if it’s really be a bug of firefox 3.6 and newer. However this both version are the only one who have this bug. All other competition browser (IE, Chrome, Safari, Opera, FF 3.5.7) works well. Thanks a lot Regards Thiemo Reproducible: Always Steps to Reproduce: 1. Goto http://www.festo.com/cms/de_de/2384.htm or http://www.festo.com/cms/de_de/628.htm) 2. Try to click a tab Basisdaten | Elektrik | Pneumatik 3. There is no link behind this tabs (only FF 3.6 and newer!) Expected Results: works like in 3.5.7 or older
Keywords: css-moz
Version: unspecified → 3.6 Branch
Confirmed with Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.3a4pre) Gecko/20100316 Minefield/3.7a4pre Only a few pixels on top of the tabs are link-sensible. And it is a regression from 3.5, true.
Component: General → Style System (CSS)
Product: Firefox → Core
QA Contact: general → style-system
Version: 3.6 Branch → Trunk
Does the regression range match when bug 238072 landed? When that happened, we started supporting display:block generated content on display:inline elements. That change was to match an equivalent change in the spec, which used to say that such generated content would be forcibly changed to display:inline, but now allows it to really be display:block. Was this site depending on the display:block being forcibly changed to display:inline?
(In reply to comment #2) > Does the regression range match when bug 238072 landed? In other words, from http://hg.mozilla.org/mozilla-central/pushloghtml?changeset=a159ad4bdb90 , between the 2008-08-17 and 2008-08-18 nightly builds on mozilla-central? Hmmm. That sounds like it's probably too old and would have been in 3.5, though I'm not sure of that off the top of my head. Maybe it was related to a more recent frame construction change?
Is there a reason for stating confirmed but not confirming the bug or is it just being forgetful? Regression range: works: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2a1pre) Gecko/20090305 Minefield/3.2a1pre http://hg.mozilla.org/mozilla-central/rev/5e81fbdd55e4 broken: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2a1pre) Gecko/20090306 Minefield/3.2a1pre http://hg.mozilla.org/mozilla-central/rev/3270fd0db0f0 http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=5e81fbdd55e4&tochange=3270fd0db0f0
Your website seems to work correctly now. Did you find a work around? Is there still a page with the issue?
(In reply to comment #5) > Your website seems to work correctly now. Did you find a work around? Is > there still a page with the issue? We have modified our Stylesheets, because the failure was no longer acceptable from our customers. If it's necessary, we can provide the old stylesheets.
Yes, if you can provide a page that shows the problem (ideally as a zip file attached to this bug, but a live link somewhere would be great too), that would be very helpful.
Marking incomplete for the time being... Please reopen if you do attach or link to a testcase that shows the problem.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.