Open
Bug 1147280
Opened 11 years ago
Updated 11 years ago
FIND should be disabled on pages with disablefastfind=true
Categories
(SeaMonkey :: UI Design, defect)
Tracking
(Not tracked)
NEW
People
(Reporter: RainerBielefeldNG, Unassigned)
References
Details
Steps how to reproduce with EN-US Seamonkey 2.33.1 (German Language pack) Gecko/20100101 Build 20150321194901 (Default Theme) on German WIN7 64bit
0. Launch Browser
1. Type into URL input line "about:addons" ► [Enter]
» List withinstalled add-ons appears
2. Menu 'View ► Page source text' ► <control+f> for "find" ►
type "disablefastfind" into search string input line
» "disablefastfind="true">" will be found
3. Return to addons list
4. Menu 'Edit ► find' (not greyed, active menu item)
» Find bar appears
5. type "disablefastfind" into search string input line
» Nothing found, imposible to search on this page
Bug: "Find" should be inactive due to "disablefastfind" tag
Additional info:
a) Explications for fastfind tag on
<https://developer.mozilla.org/en-US/docs/Mozilla/Tech/XUL/Attribute/disablefastfind>
b) for pages with this tag find bar even should disappear if it has
been activated due to "Bug 967517 - Find bar is not hidden on
disablefastfind pages"
c) in FireFox 36.0.4 menu item 'Edit ► Find' is inactive on "about:addons",
and <control+f> will activate caret in "find addon" inout line at
top right end of page, what is plausible.
But find bar will not disappear if it has been active for previous
page contents, what is Bug 967517
d) So it is even worse in SeaMonkey, where 'Edit ► Find' and <control+f>
show their normal behavior, what is not intended behavior
Comment 1•11 years ago
|
||
We would need to port from Firefox:
Bug 569342 - Find bar should not be enabled in about:addons
Bug 632233 - XULBrowserWindow.onLocationChange looks for a "disablefastfind" attribute in all content documents before ruling them out because their URI scheme isn't "about" or "chrome"
Bug 567306 - Find command (Ctrl+F) fails to pick up selected text from the page
Status: UNCONFIRMED → NEW
Ever confirmed: true
You need to log in
before you can comment on or make changes to this bug.
Description
•