Closed Bug 561071 Opened 15 years ago Closed 15 years ago

Dropping a link to contentsarea security policy is different from Branch build

Categories

(Toolkit Graveyard :: Security, defect)

Product:
Toolkit Graveyard
Component:
Security
Platform:
x86
Windows 7
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED INVALID

People

(Reporter: alice0775, Unassigned)

References

Details

No description provided.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.3a5pre) Gecko/20100421 Minefield/3.7a5pre ID:20100421041252 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.3a5pre) Gecko/20100421 Minefield/3.7a5pre ID:20100421041252 Droping a link to contentsarea security policy is different from Branch build. is this the behavior is by design? Reproducible: Always Steps to Reproduce: 1. Start Minefield with new profile. 2. Create a bookmark 'about:config' on bookmarks toolbar 3. Open http://www.mozilla.org/projects/minefield/ 4. Drag and drop the created bookmarks 'about:config' onto contentsarea. Actual Results: about:config page will be open in current tab Expected Results: should denined. and logged as follows. "Security Error: Content at chrome://browser/content/browser.xul may not load or link to about:config."
Blocks: 545714
Status: NEW → UNCONFIRMED
Ever confirmed: false
This security check is Firefox/toolkit code, not core. Gavin's touched this recently so might know whether this was on purpose.
Component: Drag and Drop → Security
Product: Core → Toolkit
QA Contact: drag-drop → toolkit
Summary: Droping a link to contentsarea security policy is different from Branch build → Dropping a link to contentsarea security policy is different from Branch build
Sounds like this may be a regression of bug 546909 caused by bug 545714.
Well, not of bug 546909 directly. The key difference here may be that the bookmark itself is being dropped, rather than just a URL.
Gavin, is there a bug here? Dragging an about: url from the bookmarks toolbar to the content area doesn't seem like it would intentionally be prevented.
Yeah, I guess this is actually a fix. Bug 546909 wasn't regressed.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → INVALID
So, Is the behavior intentional?
Yes. Do you see a problem with that?
No ploblem. But I am uneasy using Firefox. Thanks.
Product: Toolkit → Toolkit Graveyard
You need to log in before you can comment on or make changes to this bug.