Please report any other irregularities here.
Need to work this into the frame reflow method
Bulk moving old [donttest] code to new donttest keyword. Sorry for the spam!
Non PDT+, moving out.
Target Milestone: M14 → M16
Status: NEW → ASSIGNED
Target Milestone: M16 → M20
This bug has been marked "future" because the original netscape engineer working on this is over-burdened. If you feel this is an error, that you or another known resource will be working on this bug,or if it blocks your work in some way -- please attach your concern to the bug for reconsideration.
Target Milestone: M20 → Future
QA Contact update
QA Contact: petersen → amar
Bulk reassignin HTML FRAME/IFRAME bugs to Eric.
Assignee: pollmann → evaughan
Status: ASSIGNED → NEW
Bulk re-assigning all of Eric's HTMLFrame bugs to John.
Assignee: eric → jkeiser
Adding testcase, but this bug depends on others to make scrolling="yes|no" etc. work at all.
Summary: Dynamic changing of SCROLL attribute → Dynamic changing of SCROLLING attribute
I think this is the same thing. When using Mozilla to view the helpfiles of FlashMX or Director, the contents section [which dynamically opens and closes] is in a frame with scroll=yes. But if the info isn't large enough to require a scrollbar there's just this black box that sits at the top.
The main problem here is that overflow changes trigger reframe (NOT in the HTML frame sense) and that the frame constructor (again, not in the HTML frame sense) has no idea how to handle subdocument frames, really.
Assignee: john → nobody
QA Contact: amar → layout.html-frames
You need to log in before you can comment on or make changes to this bug.