Closed
Bug 280708
Opened 20 years ago
Closed 20 years ago
[FIX]hang/freeze when hovering over input (using input:hover,td:hover {display:table-row-group}
Categories
(Core :: Layout: Tables, defect, P1)
Core
Layout: Tables
Tracking
()
VERIFIED
FIXED
mozilla1.8beta1
People
(Reporter: martijn.martijn, Assigned: bzbarsky)
Details
(Keywords: regression, testcase)
Attachments
(2 files)
327 bytes,
text/html
|
Details | |
7.54 KB,
patch
|
bernd_mozilla
:
review+
roc
:
superreview+
|
Details | Diff | Splinter Review |
See upcoming testcase. Current trunk builds hang/freeze when hovering over the <input> in the testcase. This happens because I Used input:hover{display:table-row-group;} td:hover{display:table-row-group;} as css rules.
Reporter | ||
Comment 1•20 years ago
|
||
Martijn, as usual bugs like this need to get prioritized. The main criteria for me is regression. Can you try this with FF 1.0 (class:somehow old, should be fixed for 1.1) and even Seamonkey 1.6 (class: ancient, we need to fix this but 1.1 is not a milestone)
Reporter | ||
Comment 3•20 years ago
|
||
Ah, ok. I'm testing (semi-)randomly, that's why I wasn't testing it in older builds, but I'll do that from now on. It doesn't freeze/hang with: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b) Gecko/20050124 Firefox/1.0+ But it does freeze hang with: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b) Gecko/20050125 Firefox/1.0+ Maybe a regression from fixing bug 269566?
Reporter | ||
Updated•20 years ago
|
Keywords: regression
Assignee | ||
Comment 4•20 years ago
|
||
Yeah, probably... I'll look into this one.
Assignee | ||
Comment 5•20 years ago
|
||
This is effectively the same as the patch for bug 275746 (and backs that patch out, really), but I've pushed the code down into CreateAnonymousFrames, since all callers of the method would need to do this.... In particular, <input> creates anonymous frames for the editor inside it, so needs this.
Assignee: nobody → bzbarsky
Status: NEW → ASSIGNED
Attachment #173187 -
Flags: superreview?(roc)
Attachment #173187 -
Flags: review?(bernd_mozilla)
Assignee | ||
Updated•20 years ago
|
OS: Windows XP → All
Priority: -- → P1
Hardware: PC → All
Summary: hang/freeze when hovering over input (using input:hover,td:hover {display:table-row-group} → [FIX]hang/freeze when hovering over input (using input:hover,td:hover {display:table-row-group}
Target Milestone: --- → mozilla1.8beta
Attachment #173187 -
Flags: superreview?(roc) → superreview+
Boris, is this really correct given the fact that even ConstructTableFrame calls CreateAnonymousFrames?
Assignee | ||
Comment 7•20 years ago
|
||
I think it's correct, yes. Note that the very first line in CreateAnonymousFrames (the version that ConstructTableFrame calls, not the one I changed; the latter is called by the former) bails out if the node is not a root (which is a table never claims to be) and if the tagname isn't in a specific list. Also note that I'm only doing this pseudo thing if the tag is one we want to craete anonymous content for (so the inner method got called) _and_ the parent frame QIs to nsIAnonymousContentCreator (which table frames do not) _and_ it creates anonymous content. This isn't the "totally right" fix, since anonymous content with table display types should really share pseudo-frames with non-anonymous kids with table display types. But that's something that would be easier to fix with a general pseudo-frames revamp...
Attachment #173187 -
Flags: review?(bernd_mozilla) → review+
Assignee | ||
Comment 8•20 years ago
|
||
Just for reference, the parts of the diff that deal with iterators and ProcessAttachedQueue were not supposed to be there... I'll remove them before checking in.
Assignee | ||
Comment 9•20 years ago
|
||
Fixed.
Status: ASSIGNED → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
Comment 10•20 years ago
|
||
Upon hovering over the test case, the text box moves off to the right. Is this expected behaviour?
Reporter | ||
Comment 11•20 years ago
|
||
Ger, that's a known bug (don't know the bug number), but unrelated to this bug. When this bug is fixed (which it should in 20050204 trunk build), it should indeed show that behavior you described (and not hang/freeze).
The reftest 280708-1a.html actually failed on all Tinderbox platforms, so I marked it as expected-fail and filed bug 473824 for it.
You need to log in
before you can comment on or make changes to this bug.
Description
•