Closed
Bug 514308
Opened 16 years ago
Closed 16 years ago
Support shift+click of the RSS icon in the address bar
Categories
(Firefox Graveyard :: RSS Discovery and Preview, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
Firefox 3.7a1
People
(Reporter: mozilla.bugs, Assigned: mozilla.bugs)
Details
Attachments
(1 file, 3 obsolete files)
|
1.18 KB,
patch
|
Details | Diff | Splinter Review |
When testing Bug 304458, everything works except shift+click, which was requested in comment #2. I don't know if this is a regression or if that feature never made it into the patch.
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2a2pre) Gecko/20090901 Namoroka/3.6a2pre (.NET CLR 3.5.30729) ID:20090901050855
| Assignee | ||
Comment 1•16 years ago
|
||
In testing this further, when shift+click is fired on a feed, this is in the console:
Error: uncaught exception: [Exception... "Could not convert JavaScript argument arg 0 [nsISupportsArray.AppendElement]" nsresult: "0x80570009 (NS_ERROR_XPC_BAD_CONVERT_JS)" location: "JS frame :: chrome://browser/content/utilityOverlay.js :: openUILinkIn :: line 195" data: no]
http://mxr.mozilla.org/mozilla-central/source/browser/base/content/utilityOverlay.js#195
| Assignee | ||
Comment 2•16 years ago
|
||
I think I've traced the fault to http://mxr.mozilla.org/mozilla-central/source/browser/base/content/browser.js#6133
I assume we need to make sure that the event and href are properly passed to the loadFeed function, which calls the error in openUILinkIn(). I will get a patch to sniff for the shiftKey and hand the correct arguments.
Assigning to me.
Assignee: nobody → mozilla.bugs
Status: NEW → ASSIGNED
| Assignee | ||
Comment 3•16 years ago
|
||
It's caused by the inability to append allowThirdPartyFixup to sa in the function definition openUILinkIn.
Attachment #401150 -
Flags: review?(sayrer)
Updated•16 years ago
|
Attachment #401150 -
Flags: review?(sayrer) → review?(mano)
Comment 4•16 years ago
|
||
Should allowThirdPartyFixup be a nsISupportsPRBool?
| Assignee | ||
Comment 5•16 years ago
|
||
(In reply to comment #4)
> Should allowThirdPartyFixup be a nsISupportsPRBool?
I can't remember, what is it currently defined as?
| Assignee | ||
Comment 6•16 years ago
|
||
I tried setting it as a nsISupportsPRBool, but it didn't have any effect. I did discover that the function cannot append a false value, but it can append a null value, if the null value is defined within the function, but if it is sent to the function as an argument, the function fails (despite the value of the argument being null).
Also, the openUILink function has 7 arguments, while only six were provided, but fix them didn't solve this problem.
Comment 7•16 years ago
|
||
I wonder why we're using an nsISupportsArray anyway. Seems unnecessary to me.
Comment 8•16 years ago
|
||
Comment on attachment 401150 [details] [diff] [review]
Added try/catch to utilityOverlay.js to prevent appending allowThirdPartyFixup
This just hides the bug.
I cannot see why nsISupportsBool wouldn't work though... Can you post that patch?
Attachment #401150 -
Flags: review?(mano) → review-
| Assignee | ||
Comment 9•16 years ago
|
||
It doesn't work if you are dumb like me and forget to write to the value of allowThirdPartyFixup to the data attribute and not overwrite the new nsISupportsPRBool itself thus defeating the purpose of the new variable.
I think I will go somewhere quiet to contemplate my own stupidity...
Attachment #401150 -
Attachment is obsolete: true
Attachment #411029 -
Flags: review?(mano)
Comment 10•16 years ago
|
||
Comment on attachment 411029 [details] [diff] [review]
Patch v 1.1
I would call it allowThirdPartyFixupSupports.
r=mano. A test would be nice.
Attachment #411029 -
Flags: review?(mano) → review+
| Assignee | ||
Comment 11•16 years ago
|
||
Ideally, we should test Bug 304458 which this was originally part of but was never tested. The original bug added ctrl+click and several similar behaviors, so we should do a test for all of these at once.
I have requested in-testsuite on the first bug, so it's on my radar, and I'll also request on this so that it is all the more on my radar.
Flags: in-testsuite?
Keywords: checkin-needed
| Assignee | ||
Comment 12•16 years ago
|
||
Changed the variable name, and now it needs check-in.
Attachment #411029 -
Attachment is obsolete: true
Attachment #411209 -
Flags: approval1.9.2?
| Assignee | ||
Comment 13•16 years ago
|
||
Yikes! Never mind...
The other file had the fix for another bug in it. This one doesn't.
Attachment #411209 -
Attachment is obsolete: true
Attachment #411211 -
Flags: approval1.9.2?
Attachment #411209 -
Flags: approval1.9.2?
Comment 14•16 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 16 years ago
Keywords: checkin-needed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 3.7a1
| Assignee | ||
Comment 15•16 years ago
|
||
Verified Fixed.
Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.3a1pre) Gecko/20091110 Minefield/3.7a1pre (.NET CLR 3.5.30729) ID:20091110052734
Status: RESOLVED → VERIFIED
Comment 16•16 years ago
|
||
Comment on attachment 411211 [details] [diff] [review]
Patch v 1.2 - correct
approval1.9.2 requests aren't currently being monitored, since we're nearing RC freeze and there are too many outstanding requests, so I'm clearing this request. Feel free to re-request approval if you are confident that it's worth drivers' time to consider whether this non-blocker needs to land for 1.9.2 at this stage.
Attachment #411211 -
Flags: approval1.9.2?
Updated•7 years ago
|
Product: Firefox → Firefox Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•