Closed
Bug 256029
Opened 21 years ago
Closed 21 years ago
OK doesn't work after changing home page and switching to another category
Categories
(Firefox :: Settings UI, defect)
Tracking
()
VERIFIED
FIXED
People
(Reporter: bugzilla, Assigned: p_ch)
Details
(Keywords: fixed-aviary1.0, Whiteboard: [have patch] - ready to land)
Attachments
(1 file, 2 obsolete files)
8.48 KB,
patch
|
p_ch
:
review+
asa
:
approval-aviary+
|
Details | Diff | Splinter Review |
couldn't find an exising bug which covers this. found using 2004081708-0.9+
firefox bits on linux (fedora 2); Tracy also sees this on today's Windows
aviary1.0 bits.
OK doesn't work after changing home page and switching to another category.
1. open Preferences (Options) and go to the General category.
2. manually (using keyboard) change the Home Page.
3. click another category (Advanced, Privacy, etc.).
4. click OK (or hit Enter) to save and dismiss Preferences.
expected: Prefs dlg should go away.
actual results: nothing happens, Prefs dlg persists. no js console output. :-\
workaround: go back to the General category, and OK/Enter work again.
![]() |
Reporter | |
Comment 1•21 years ago
|
||
if the fix is trivial, could this make it for PR? if not, then [also] nominating
for 1.0.
Flags: blocking-aviary1.0PR?
Flags: blocking-aviary1.0?
Comment 2•21 years ago
|
||
We can't ship with this. If not PR, then definitely final.
Flags: blocking-aviary1.0? → blocking-aviary1.0+
![]() |
||
Comment 3•21 years ago
|
||
I think we need to fix this for PR.
Assignee: firefox → p_ch
Flags: blocking-aviary1.0PR? → blocking-aviary1.0PR+
![]() |
||
Comment 4•21 years ago
|
||
we're breaking here:
http://lxr.mozilla.org/aviarybranch/source/browser/components/prefwindow/content/pref-navigator.js#102
blame is bryner's, cheap hack is to just take the bits from utilityOverlay.js
and use those directly in the onOK function.
![]() |
Assignee | |
Comment 5•21 years ago
|
||
This bug happens because |onOK()| is called as a callback function in a js
context in which |getShellService()| is not defined.
Unless lxr is drunk, there is no use of shouldBeDefaultBrowser in the code
base, but anyways the 'default browser' action is set on the fact, so we can
safely get rid of it in |onOK|.
There was two parallel switches to determine if the shell service is
implemented or not: one at run-time, and the other at compile-time. I am not
keen on making use of the xul/js preprocessor other than for platforms
discrimination and I think it's more confusing than helpful, I then removed the
preprocessor switch.
![]() |
Assignee | |
Updated•21 years ago
|
Attachment #156901 -
Flags: review?(bryner)
![]() |
Assignee | |
Comment 6•21 years ago
|
||
Updated•21 years ago
|
Whiteboard: [have patch] need bryner review
![]() |
||
Comment 7•21 years ago
|
||
Comment on attachment 156901 [details] [diff] [review]
patch v1.0 diff -uw
What's with the all-caps variable naming? We don't use that anywhere else in
the frontend code that I can find. Change it to shellSvc or shellService and
r=bryner.
Attachment #156901 -
Flags: review?(bryner) → review+
![]() |
Assignee | |
Comment 8•21 years ago
|
||
(In reply to comment #7)
> (From update of attachment 156901 [details] [diff] [review])
> What's with the all-caps variable naming? We don't use that anywhere else in
> the frontend code that I can find. Change it to shellSvc or shellService and
> r=bryner.
>
there are a lot of such instances: search.xml, printUtils.js, bookmarks.js.
The function initServices() in bookmarks.js was even planned (long long time
ago) to be moved to browser.js and make use of it.
I am not the investigator of such a convention (BMSVC, RDF, RDFCU predate my
involvement) but I sticked with it and therefore spread it.
I think that the all-caps convention for services is a good one that makes clear
that we are dealing with an interface.
Updated•21 years ago
|
Whiteboard: [have patch] need bryner review → [have patch] - ready to land
![]() |
Assignee | |
Comment 9•21 years ago
|
||
the pref component doesn't use the all-caps convention for services, let's use
shellSvc.
(the only difference between the -u and -uw diff is an indentation correction
in the default browser groupbox)
Attachment #156901 -
Attachment is obsolete: true
Attachment #156903 -
Attachment is obsolete: true
![]() |
Assignee | |
Comment 10•21 years ago
|
||
Comment on attachment 157474 [details] [diff] [review]
patch v1.1 diff -uw
marking bryner's r+ and requesting aviary approval.
Attachment #157474 -
Flags: review+
Attachment #157474 -
Flags: approval-aviary?
Comment 11•21 years ago
|
||
Comment on attachment 157474 [details] [diff] [review]
patch v1.1 diff -uw
a=asa for aviary checkin
Attachment #157474 -
Flags: approval-aviary? → approval-aviary+
![]() |
Assignee | |
Comment 12•21 years ago
|
||
checked in trunk+aviary branch
Comment 13•21 years ago
|
||
regression on mac:
http://bugzilla.mozilla.org/show_bug.cgi?id=258110
Comment 14•21 years ago
|
||
verfied with Windows Firefox branch build 2004-09-09-08-0.9
Status: RESOLVED → VERIFIED
![]() |
||
Comment 15•19 years ago
|
||
sorry for bugspam, long-overdue mass reassign of ancient QA contact bugs,
filter on "beltznerLovesGoats" to get rid of this mass change
QA Contact: mconnor → preferences
You need to log in
before you can comment on or make changes to this bug.
Description
•