Bug 24064

Summary: REGRESSION: Legend not hidden with display:none
Product: WebKit Reporter: Jan Boeijink <jjj>
Component: CSSAssignee: Nobody <webkit-unassigned>
Status: RESOLVED FIXED    
Severity: Normal CC: ap, flosch, hyatt, martin, zerok
Priority: P1 Keywords: HasReduction, Regression
Version: 528+ (Nightly build)   
Hardware: Mac   
OS: OS X 10.4   
Attachments:
Description Flags
Fieldset with legend (display:none) none

Jan Boeijink
Reported 2009-02-20 11:28:07 PST
Legend element is not hidden with display:none. Works okay in current Safari or FF, not in nightly builds.
Attachments
Fieldset with legend (display:none) (212 bytes, text/html)
2009-02-20 11:30 PST, Jan Boeijink 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Jan Boeijink
Comment 1 2009-02-20 11:30:48 PST
Created attachment 27834 [details] Fieldset with legend (display:none)
Horst Gutmann
Comment 2 2009-02-25 01:53:59 PST
I assume this is also what breaks the rendering of identi.ca: http://zerokspot.com/uploads/snapshots/identica.webkit-20090225-104926.jpg
Alexey Proskuryakov
Comment 3 2009-02-25 07:10:35 PST
(In reply to comment #2) > I assume this is also what breaks the rendering of identi.ca: That's unlikely to be the same issue, please file a new bug. And I cannot reproduce it with r41181 (although this might be because I'm getting Russian language interface on this site).
Horst Gutmann
Comment 4 2009-02-25 07:24:05 PST
Well, the problem from what I can tell *is* that a legend element isn't hidden when declared display:none in the associated stylesheet. http://zerokspot.com/uploads/snapshots/webkit.identica.legend-20090225-162214.jpg Note that the buttons are only available when being logged in and so this problem should only be visible then.
Alexey Proskuryakov
Comment 5 2009-03-12 02:36:19 PDT
I cannot reproduce the problem with a recent build any more (using the attached test case). Could you please check if the problem at identi.ca is fixed, too?
Horst Gutmann
Comment 6 2009-03-12 03:29:00 PDT
Yes, seems to have been fixed in a recent build :D
Jan Boeijink
Comment 7 2009-03-12 03:42:57 PDT
I guess it was solved in changeset 41538. Nice.
Note You need to log in before you can comment on or make changes to this bug.