Closed
Bug 264812
Opened 20 years ago
Closed 20 years ago
Text under back and forward buttons is not grayed out
Categories
(Camino Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jpellico, Assigned: mozilla)
Details
Attachments
(1 file)
|
1.46 KB,
patch
|
Details | Diff | Splinter Review |
Open a new browser window in Camino. The Back and Forward icons will be dimmed, but the text beneath them will not. This persists whenever these icons are enabled and disabled again.
Haha I saw this one long time ago but never filed a bug, good catch.
| Reporter | ||
Comment 2•20 years ago
|
||
I have also seen the text grayed out when the icons are enabled! Crrrrrazy!
| Assignee | ||
Updated•20 years ago
|
Assignee: pinkerton → Bruce.Davidson
| Assignee | ||
Comment 4•20 years ago
|
||
This patch fixes the enabled/disabled state of the text under the back and forward buttons. We just need to call setEnabled: on the entire toolbar button rather than just the view (the icon bit that provides the drop-downness). Requesting r= from someone prior to requesting sr= from pinkerton.
| Assignee | ||
Updated•20 years ago
|
Attachment #163196 -
Flags: review?
Calling setEnabled on the view alone looks pretty explicit in the existing code. Do you know why the author might have done that? This will need a lot of testing, perhaps especially with regards to context menu history.
| Assignee | ||
Comment 6•20 years ago
|
||
Yeah, I had that concern too. I don't know why it was written like this. The testing I've done so far can be summarised as: (back/forward possible) 00 01 10 11 icon & text okay okay okay okay (previously text was wrong) icon only okay okay okay okay (unchanged) text only wrong wrong wrong okay (unchanged) context menu okay okay okay okay (unchanged) menu bar okay okay okay okay (unchanged) With a text only toolbar the two toolbar items are always enabled both before and after applying the patch. (Thanks for your comment, which prompted that test.) I'll have another look tomorrow to see if I can see why that is. I suspect icon & text is much more common, and as the current inconsistency between the icon and text state is quite noticeable and confusing. If its not obvious it might be better to spin that bit off to a separate bug.
| Reporter | ||
Comment 7•20 years ago
|
||
While you're at it, could you fix it so that clicking on the text when the icon is enabled, works like it does for normal toolbar buttons? ;-)
| Assignee | ||
Comment 8•20 years ago
|
||
Comment on attachment 163196 [details] [diff] [review] Proposed patch Clearing the review flag for this patch based on latest comment. Enabling the text only to ignore the user click on it is a Bad Thing (tm). I'll try to have a look at the weekend to see if I can get a patch that fixes this more completely.
Attachment #163196 -
Flags: review?
| Reporter | ||
Comment 9•20 years ago
|
||
I don't think it's a negative consequence of the patch. I do think that we should expand this bug to any deficiencies in the behavior of the back/forward buttons. Before, label always enabled but you can never click on the label. Desired: label is enabled => you can click on it. Shouldn't be much more work ;-)
| Assignee | ||
Comment 10•20 years ago
|
||
Turns out that smfr checked this fix in in v1.165 of BrowserWindowController.mm, whilst addressing another problem. Resolving as fixed. (The "always enabled in text only mode" appears to affect other apps too, e.g. XCode, so is probably not a Camino problem.)
Status: ASSIGNED → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•