Closed
Bug 137982
Opened 22 years ago
Closed 22 years ago
Page elements are sometimes misdrawn as grey boxes or in wrong position
Categories
(Core :: Layout, defect, P2)
Tracking
()
VERIFIED
FIXED
mozilla1.0.2
People
(Reporter: bugmail, Assigned: dcone)
References
()
Details
(Keywords: testcase, top100, topembed+, Whiteboard: Self-explanatory testcase at URL above)
Attachments
(4 files)
105.90 KB,
image/png
|
Details | |
116.94 KB,
image/png
|
Details | |
585 bytes,
patch
|
Details | Diff | Splinter Review | |
1.71 KB,
patch
|
dcone
:
review+
sfraser_bugs
:
superreview+
asa
:
approval+
|
Details | Diff | Splinter Review |
From Bugzilla Helper: User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.0rc1) Gecko/20020416 BuildID: 2002041618 Page display corrupts if the Bugzilla Query Page has to reload to do its' "adding form fields" operation. Reproducible: Always Steps to Reproduce: 1. Access the Bugzilla Query Page 2. Type some text into the Summary field 3. Submit the query Actual Results: Bugzilla does its' "adding form fields" operation (I still have no idea what or why Bugzilla does that, but that's another story) and redisplays the Query Page, but display is corrupt. Expected Results: Page display should not have been corrupt. A screenshot will shortly be attached hereon.
Comment 2•22 years ago
|
||
Are you using XBL form controls or regular form controls?
I have this problem too. To reproduce, load http://bugzilla.mozilla.org/query.cgi scroll to the bottom of the page and type "form control" in the Summary field, then press enter. I have had this problem for a while; it is not new in this build.
Confirmed on 2002041710 on Mac OS 9.2.2. Changing OS to All as not limited to Mac OS X.
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: MacOS X → All
Keywords: mozilla1.0
Comment 7•22 years ago
|
||
Confirming issue on OSX (2002-26-05) branch. Setting Priority to P2.
Priority: -- → P2
Comment 8•22 years ago
|
||
I mean 2002-04-26-05 OS X branch.
Comment 9•22 years ago
|
||
I just tried this in the latest OS X build (2002-05-03-09) and can't reproduce. Anyone see this issue with the same build ?
Reporter | ||
Comment 10•22 years ago
|
||
It doesn't reproduce because my steps no longer cause the Query page to reload. Does anyone know what condition causes the Query page to reload with that "adding query fields" nonsense?
Reporter | ||
Comment 11•22 years ago
|
||
*** Bug 141665 has been marked as a duplicate of this bug. ***
Reporter | ||
Comment 12•22 years ago
|
||
*** Bug 148050 has been marked as a duplicate of this bug. ***
Reporter | ||
Comment 13•22 years ago
|
||
*** Bug 151569 has been marked as a duplicate of this bug. ***
Reporter | ||
Comment 14•22 years ago
|
||
I suspect this may be related to my bug 152064.
Reporter | ||
Comment 15•22 years ago
|
||
Note that this still occurs using FizzillaCFM/2002062203.
Comment 16•22 years ago
|
||
*** Bug 152064 has been marked as a duplicate of this bug. ***
Reporter | ||
Comment 17•22 years ago
|
||
Changing this bug to better reflect the problem, seeing that Bug 152064 has been duplicated to this. I also made a better testcase on that bug than on this one. Adding its' URL to this bug. To use the testcase: 1. Access the testcase URL 2. Click the "Link with hash" Actual Results: A grey box was drawn in the upper-left position of the content pane, in the same position the real IFRAME would be drawn if the URL was accessed without the hash portion (try the "Hashless link" for comparison). Expected Results: The grey box should not have been drawn at all, and the text underneath should have been completely visible. Scrolling the page doesn't correct display, but resizing the window does.
Summary: Navigator display corrupts after form submission/redisplay → Page elements are sometimes misdrawn as grey boxes
Summary: Page elements are sometimes misdrawn as grey boxes → Page elements are sometimes misdrawn as grey boxes or in wrong position
Reporter | ||
Comment 18•22 years ago
|
||
*** Bug 156260 has been marked as a duplicate of this bug. ***
Comment 19•22 years ago
|
||
Currently the query page displays with gray boxes when you press Back while viewing a query result.
Comment 21•22 years ago
|
||
*** Bug 157042 has been marked as a duplicate of this bug. ***
Reporter | ||
Comment 22•22 years ago
|
||
*** Bug 158955 has been marked as a duplicate of this bug. ***
Reporter | ||
Comment 23•22 years ago
|
||
FWIW, this bug appeared between 0.9.9 (2002031005) and 1.0RC1 (2002041712).
Reporter | ||
Comment 24•22 years ago
|
||
Per comment 5, setting OS to 9.x. All would have to include Linux.
OS: All → Mac System 9.x
Comment 25•22 years ago
|
||
John, Any status update on resolving this bug ?
Reporter | ||
Comment 26•22 years ago
|
||
*** Bug 160844 has been marked as a duplicate of this bug. ***
Comment 28•22 years ago
|
||
*** Bug 161916 has been marked as a duplicate of this bug. ***
Reporter | ||
Comment 29•22 years ago
|
||
*** Bug 162045 has been marked as a duplicate of this bug. ***
Keywords: mozilla1.0
Whiteboard: Self-explanatory testcase at URL above
Comment 31•22 years ago
|
||
*** Bug 163311 has been marked as a duplicate of this bug. ***
*** Bug 148572 has been marked as a duplicate of this bug. ***
Copying over screenshot from bug 148572. This is a funny one, I saw the grey boxes, but Grab.app saw this instead. I have no idea what to make of that.
Reporter | ||
Comment 34•22 years ago
|
||
*** Bug 164267 has been marked as a duplicate of this bug. ***
Comment 35•22 years ago
|
||
I posted one of the dups for this bug, but it's still present under 1.1 Final on OS X (10.1.5). I notice this happens most often (for me) on Bulletin Board systems that use Open Topic. For example, over at Ars Technica this occurs *every* time I refresh a thread page I have posted to. They are now using Open Topic 2.3.0.
Reporter | ||
Comment 36•22 years ago
|
||
*** Bug 165475 has been marked as a duplicate of this bug. ***
Reporter | ||
Comment 37•22 years ago
|
||
*** Bug 166116 has been marked as a duplicate of this bug. ***
Assignee | ||
Comment 38•22 years ago
|
||
Invisible elements need to be scrolled also, seems the IFrames are set invisible when they are scrolled offscreen initially. This fix lets these frames move themselves off the screen and sync up. This check is not on any other platform. Mac is unique in that we have to maintain the offset of these windows ourselves so breakin from the scroll code was not a good thing.
Comment 39•22 years ago
|
||
Comment on attachment 99112 [details] [diff] [review] removed a check in scroll for visibility. r=rods
Comment 40•22 years ago
|
||
Comment on attachment 99112 [details] [diff] [review] removed a check in scroll for visibility. You should ensure that this change doesn't regress page load performance, or scrolling performance, by causing unucessary invalidates, especially when browsing with multiple tabs.
Comment 41•22 years ago
|
||
Also, how does this relate to the work that roc+moz@cs.cmu.edu has been doing?
I think I have duplicates of this bug filed against me. As far as I know these problems are all Mac-only.
Assignee | ||
Comment 43•22 years ago
|
||
if I leave that check in.. IFrames and some other widgets are drawn incorrectly using the back button or an anchor tag on a page going to another page. Performance is really secondary to the page looking right in this case. If the performance does degrade on page loads that are pre-scrolled.. the performance will have to be fixed some other way.. because the offsets need to be set for these windows when things are scrolled.. right? also 1.) The routine I put the fix in "::scroll" is a very small part of this performance fix. 2.) The routine I put the fix in is only hit for a page load if the page is scrolled before the load (like a page back or page forward). So for normal page loads this routine is not hit and can not degrade the load performance. 3.) When it is hit for a page load.. it really needs to do the things in that routine so it can sync up the offsets. 4.) Just to make sure I did page loads that were not pre-scrolled and this routine was not called.
Comment 44•22 years ago
|
||
This patch seems more sensible to me: only do the invalidation stuff in Scroll if the widget is visible, but always move the child widgets, and recalc window regions.
Comment 45•22 years ago
|
||
*** Bug 148075 has been marked as a duplicate of this bug. ***
Assignee | ||
Comment 46•22 years ago
|
||
Comment on attachment 99133 [details] [diff] [review] Alternative nsWindow.cpp patch r=dcone. This works with my test cases.
Attachment #99133 -
Flags: review+
Assignee | ||
Comment 47•22 years ago
|
||
can you sr this simon.. or is that against super review policy???
Comment 48•22 years ago
|
||
Comment on attachment 99133 [details] [diff] [review] Alternative nsWindow.cpp patch sr=sfraser. A fine patch indeed!
Attachment #99133 -
Flags: superreview+
Comment 49•22 years ago
|
||
Oh Frabjous day! Nominating for MOZILLA_1_0_BRANCH
Keywords: adt1.0.1,
mozilla1.0.2
Reporter | ||
Comment 50•22 years ago
|
||
Is this checked into the trunk?
Comment 51•22 years ago
|
||
Added top100, topembed+ keywords to this bug from bug 148075
Comment 52•22 years ago
|
||
This landed on trunk today but wasn't marked FIXED. Doing so now so that it'll be evaluated for MOZILLA_1_0_BRANCH
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
Comment 53•22 years ago
|
||
Nominating for the 1.0 branch, as this would be a good thing to get resolved for a mjor embeddor (e.g. topembed+, top100).
Reporter | ||
Comment 54•22 years ago
|
||
The testcase URL does now appear to work using FizzillaCFM/2002091708. Great job, dcone and sfraser!
Comment 55•22 years ago
|
||
Comment on attachment 99133 [details] [diff] [review] Alternative nsWindow.cpp patch a=asa (on behalf of drivers) for checkin to the 1.0 branch.
Attachment #99133 -
Flags: approval+
Comment 56•22 years ago
|
||
Awesome, this bug is finally dead ! Verified on OS X 2002-09-17-08 Trunk and OS 9.1 2002-09-17-08 trunk builds.
Status: RESOLVED → VERIFIED
Comment 57•22 years ago
|
||
edt1.0.2+ (per verbal from saari) approval for landing on the 1.0 branch, pending Drivers' approval. Pls land time asap, then replace "mozilla1.0.2+" with "fixed1.0.2". thanks!
Comment 58•22 years ago
|
||
Marking as "Mozilla1.0.2+" per comment Comment #55 From Asa Dotzler.
Keywords: mozilla1.0.2 → mozilla1.0.2+
Assignee | ||
Comment 59•22 years ago
|
||
The check for visiblity is not in the code for the branch.. so this problem does not exist there. I am not sure how to mark this.. since it will not be fixed on the branch since the problem does not exist there.
Comment 60•22 years ago
|
||
I'm pretty sure it is on the branch: http://lxr.mozilla.org/mozilla1.0/source/widget/src/mac/nsWindow.cpp#1871
Comment 61•22 years ago
|
||
This fix is most certainly needed on the branch as I see the incorrectly drawn grey boxes constantly in Netscape 7.0
Assignee | ||
Comment 62•22 years ago
|
||
I just repulled that file.. and I don't get those changes.. I will repull the entire branch.. see if I get it. Very very strange indeed.
Reporter | ||
Comment 63•22 years ago
|
||
Anybody have any idea what might have introduced this bug? (See comment 23.)
Assignee | ||
Comment 64•22 years ago
|
||
Re-pull updated to correct version, something is wrong with the cvs update.. need to investigate that. I checked the fix into the branch.
Keywords: mozilla1.0.2+ → fixed1.0.2
Comment 65•22 years ago
|
||
Greg: yes, I believe it was my optimization to not redraw invisible widgets.
Comment 66•22 years ago
|
||
petersen: can you pls verify this as fixed on the 1.0 branch, then replace "fixed1.0.2" with "verified1.0.2". thanks!
Comment 67•22 years ago
|
||
Verified on branch (2002-09-18-05) under OS X 10.2.
Keywords: fixed1.0.2 → verified1.0.2
Comment 68•22 years ago
|
||
*** Bug 140509 has been marked as a duplicate of this bug. ***
Reporter | ||
Comment 69•22 years ago
|
||
*** Bug 134894 has been marked as a duplicate of this bug. ***
Comment 70•22 years ago
|
||
*** Bug 138709 has been marked as a duplicate of this bug. ***
You need to log in
before you can comment on or make changes to this bug.
Description
•