Closed
Bug 491530
Opened 15 years ago
Closed 15 years ago
Dragging a tab onto homepage button doesn't set it as homepage
Categories
(Firefox :: Tabbed Browser, defect)
Tracking
()
VERIFIED
FIXED
Firefox 3.6a1
People
(Reporter: fake.fakeness, Assigned: asaf)
References
Details
(Keywords: regression, verified1.9.1, Whiteboard: [fixed by bug 487263])
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; nl; rv:1.9.1b4) Gecko/20090423 Firefox/3.5b4
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; nl; rv:1.9.1b4) Gecko/20090423 Firefox/3.5b4
In the old firefox it was possible to drag a tab onto the homepage button and you would be prompted to set your homepage to this tab. When I drag a tab onto the homepage button now nothing happens.
Thanks
Reproducible: Always
Steps to Reproduce:
1. Drag tab onto homepage button
Actual Results:
Absolutly nothing
Expected Results:
Prompt to set this tab as homepage
Reporter | ||
Updated•15 years ago
|
Version: unspecified → 3.5 Branch
Comment 1•15 years ago
|
||
Confirmed on Windows XP. Long range: http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=8bfac66fe41a&tochange=262d44d6e425
Possibly bug 475066 ?
Flags: blocking-firefox3.5?
Updated•15 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Updated•15 years ago
|
Blocks: 475066
Keywords: regression
Comment 2•15 years ago
|
||
Yes, I'm pretty sure that this is due to the tab-dragging work. Not sure I'd block Fiefox 3.5 on this, to be honest.
As an immediate workaround, you can still drag the favicon or URL from the location bar and it'll work.
Mano: I'm pretty sure that at one point I told you this would be a "nice to have" and is along the lines of bug 469176 comment 16?
Comment 3•15 years ago
|
||
This sounds the same as bug 465910 that has blocking 3.5 status. By the same logic should this bug not have the same blocking status?
Comment 4•15 years ago
|
||
(In reply to comment #3)
> This sounds the same as bug 465910 that has blocking 3.5 status.
In that case this bug needs to be marked as duplicate of bug bug 465910, and bug 465910 needs to be reopened.
Comment 5•15 years ago
|
||
This is also not working on today's trunk:
Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2a1pre) Gecko/20090506 Minefield/3.6a1pre Firefox/3.0.7 ID:20090506045618
Seeing this in Console2:
Error: transferData.first is null
Source file: chrome://global/content/nsDragAndDrop.js
Line: 458
Comment 6•15 years ago
|
||
(In reply to comment #4)
> (In reply to comment #3)
> > This sounds the same as bug 465910 that has blocking 3.5 status.
>
> In that case this bug needs to be marked as duplicate of bug bug 465910, and
> bug 465910 needs to be reopened.
This is a fixed bug and regressed again by another bug.
Comment 7•15 years ago
|
||
Correct. Same happens when you drag a tab onto the new tabs toolbar button. No new tab will be opened. It's a new regression.
Component: General → Drag and Drop
Flags: blocking-firefox3.5?
OS: Windows XP → All
Product: Firefox → Core
QA Contact: general → drag-drop
Hardware: x86 → All
Version: 3.5 Branch → 1.9.1 Branch
Updated•15 years ago
|
Flags: blocking1.9.1?
Comment 8•15 years ago
|
||
I don't see why you're moving this to Core.
Comment 9•15 years ago
|
||
Sorry, that wasn't intended.
Component: Drag and Drop → Tabbed Browser
Flags: blocking1.9.1?
Product: Core → Firefox
QA Contact: drag-drop → tabbed.browser
Version: 1.9.1 Branch → 3.5 Branch
Updated•15 years ago
|
Flags: blocking-firefox3.5?
Comment 10•15 years ago
|
||
I don't think this has anything to do with bug 465910, fwiw, I think it's more related to how we no longer pass the URL of a tab to a drop-target when the tab is dragged, which is an intentional change.
As mentioned in comment 2, if you drag the URL from the location bar it will still work. I think this is a similar issue to bug 469176, which is that tabs are no longer proxies for the URLs. Not sure if it's a straight dupe, need Mano's input.
Comment 11•15 years ago
|
||
Mano: pingpingpingpingping?
Comment 12•15 years ago
|
||
Don't think it blocks, but if we can get it for RC we should.
Assignee: nobody → mano
Flags: wanted-firefox3.5+
Flags: blocking-firefox3.5?
Flags: blocking-firefox3.5-
Assignee | ||
Comment 13•15 years ago
|
||
Fixed by bug 487263.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Whiteboard: [will be fixed by bug 487263]
Comment 14•15 years ago
|
||
Verified fixed on trunk with builds on all platforms.
Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2a1pre) Gecko/20090520 Minefield/3.6a1pre ID:20090520033508
Status: RESOLVED → VERIFIED
Whiteboard: [fixed by bug 487263]
Target Milestone: --- → Firefox 3.6a1
Comment 15•15 years ago
|
||
As long as the patch on bug 487263 doesn't get backed-out, this is also verified fixed with Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1pre) Gecko/20090521 Shiretoko/3.5pre ID:20090521135222
Keywords: verified1.9.1
You need to log in
before you can comment on or make changes to this bug.
Description
•