Closed
Bug 751948
Opened 13 years ago
Closed 12 years ago
window.innerWidth changes for background tabs
Categories
(Firefox for Android Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: bnicholson, Assigned: kats)
Details
Attachments
(1 file)
(deleted),
text/plain
|
Details |
I came across this bug while working on bug 750846.
STR:
1) Open http://people.mozilla.com/~bnicholson/test/short-page2.html
2) Observe logcat. Every 5 seconds, you should see something like:
05-04 10:34:54.551 18094 18104 E GeckoConsole: BRN: window.innerWidth = 200
05-04 10:34:49.286 18094 18104 E GeckoConsole: BRN: documentElement.scrollWidth = 200
3) Click the new tab button
4) Search for a phrase, hit Enter (or go to an about:page)
5) Logcat now shows a different value for innerWidth:
05-04 10:33:36.442 17570 17580 E GeckoConsole: BRN: window.innerWidth = 540
05-04 10:33:36.465 17570 17580 E GeckoConsole: BRN: documentElement.scrollWidth = 200
Searching a phrase or going to an about:page in step 3 is important; I found that if I clicked a URL in the AwesomeScreen, it didn't reproduce the problem.
Assignee | ||
Comment 1•13 years ago
|
||
What device were you using when you did this? I'm not able to reproduce on the Galaxy Nexus.
Reporter | ||
Comment 2•13 years ago
|
||
(In reply to Kartikaya Gupta (:kats) from comment #1)
> What device were you using when you did this? I'm not able to reproduce on
> the Galaxy Nexus.
This is on a Droid RAZR. I can't reproduce this on my Galaxy S.
Assignee | ||
Updated•13 years ago
|
Assignee: nobody → bugmail.mozilla
Assignee | ||
Comment 3•12 years ago
|
||
I got a hold of a Droid RAZR and still can't reproduce it. I get the following output always from the page:
05-30 14:00:13.624 E/GeckoConsole( 2039): BRN: window.innerWidth = 200
05-30 14:00:13.648 E/GeckoConsole( 2039): BRN: documentElement.scrollWidth = 200
05-30 14:00:13.664 E/GeckoConsole( 2039): BRN: window.innerHeight = 315
05-30 14:00:13.671 E/GeckoConsole( 2039): BRN: documentElement.scrollHeight = 8
Assignee | ||
Comment 4•12 years ago
|
||
Brian, can you please double-check to see if this is still happening for you on a recent build? If not this bug should be closed as WFM. It might have been fixed along the way somewhere since you first saw it.
Reporter | ||
Comment 5•12 years ago
|
||
(In reply to Kartikaya Gupta (:kats) from comment #4)
> Brian, can you please double-check to see if this is still happening for you
> on a recent build? If not this bug should be closed as WFM. It might have
> been fixed along the way somewhere since you first saw it.
It's still happening, but only on my local debug build. I can't reproduce it with the beta release or nightly.
Assignee | ||
Comment 6•12 years ago
|
||
That's weird. Do you have any local changes? Could you post your mozconfig?
Reporter | ||
Comment 7•12 years ago
|
||
No local changes. mozconfig attached.
Assignee | ||
Comment 8•12 years ago
|
||
I built using your mozconfig and still can't reproduce it. I think your device must be messed up :)
Assignee | ||
Comment 9•12 years ago
|
||
It seems like the only way forward is for you to post a build that reproduces the problem, and I run it on my Droid RAZR to see if it happens. I'm not sure it's even worth the effort at this point since I haven't seen this problem crop up anywhere else. If you're willing to upload an APK though I can try it.
Assignee | ||
Comment 10•12 years ago
|
||
Statute of limitations expired; closing this bug.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
Updated•4 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•