Closed
Bug 58416
Opened 25 years ago
Closed 24 years ago
Back button not functioning after a skin switch
Categories
(Core Graveyard :: Skinability, defect, P3)
Tracking
(Not tracked)
People
(Reporter: morse, Assigned: hyatt)
References
Details
Steps to reproduce:
1. From pref-panel, set homepage to be some page that has links on it
2. Exit and reenter browser.
At this point you are on the homepage and tha back button is greyed out because
there is nothing in the current history as expected
3. From the pref-panel, do a skin switch. Back button is still greyed out
4. Click on a link. New page is displayed
Expected: back button is not grey because there is a page to go back to
Actual: back button remains grey.
As you continue clicking on links, the back button remains greyed. If at some
point you get to a new page by typing it in the URL bar, then the back button
becomes ungreyed.
Reason this is happening is that the ReinitializeContentVariables() method of
nsBrowserInstance is not getting called when clicking on links but it does get
called when you type in a new url.
|
||
Comment 1•25 years ago
|
||
skinability? punt back if not...
Assignee: hyatt → ben
Component: XP Apps → Skinability
QA Contact: sairuh → blakeross
|
Reporter | |
Comment 2•25 years ago
|
||
I assigned it to hyatt as per a phone conversation I had with him. He said he
thought he knew what the problem was. He was also aware that it impacted bug
57395 which has some legal/security implications.
Assignee: ben → hyatt
|
||
Comment 4•24 years ago
|
||
Actually, this is a dup of bug 60151 "back button not working after applying
theme". Bug 60151 is already assigned and radha said understood the problem.
I'm not sure what to make of morse's comment above that "I assigned it to hyatt
as per a phone conversation I had with him" since the bug isn't assigned, but
don't think it will hurt to dupe, since the real blocker bug for this one has
been fixed.
*** This bug has been marked as a duplicate of 60151 ***
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
|
|
Reporter | |
Comment 5•24 years ago
|
||
When I said I "assigned it to hyatt", I meant that I entered hyatt's name as the
assignee. The fact that the bug was in the NEW state and not in the ASSIGNED
state merely means that the assignee had not yet accepted the bug.
|
||
Comment 6•24 years ago
|
||
hrmpf, I almost always prefer to dupe new bugs on old ones but alas, too late now.
VERIFIED Dupe
Status: RESOLVED → VERIFIED
|
||
Updated•17 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•