Closed
Bug 204810
Opened 23 years ago
Closed 23 years ago
DOM Inspector should probably add disablesecurity="true" to its <browser>s
Categories
(Other Applications :: DOM Inspector, defect)
Other Applications
DOM Inspector
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jag+mozilla, Assigned: caillon)
Details
Attachments
(1 file)
|
2.01 KB,
patch
|
jag+mozilla
:
review+
jag+mozilla
:
superreview+
sspitzer
:
approval1.4+
|
Details | Diff | Splinter Review |
This will cause us to not create and add a security UI object to the <browser>,
which I doubt DOM Inspector uses.
|
Assignee | |
Comment 1•23 years ago
|
||
Ah, I did not even know this existed. I just looked up browser.xml to see what
it does, and I agree that I probably should add this. Thanks for the heads up.
Status: NEW → ASSIGNED
|
|
Assignee | |
Comment 2•23 years ago
|
||
|
|
Assignee | |
Updated•23 years ago
|
Attachment #122724 -
Flags: superreview?(jaggernaut)
Attachment #122724 -
Flags: review?(jaggernaut)
|
Reporter | |
Comment 3•23 years ago
|
||
Comment on attachment 122724 [details] [diff] [review]
Patch
r+sr=jag
Attachment #122724 -
Flags: superreview?(jaggernaut)
Attachment #122724 -
Flags: superreview+
Attachment #122724 -
Flags: review?(jaggernaut)
Attachment #122724 -
Flags: review+
Attachment #122724 -
Flags: approval1.4?
|
|
||
Comment 4•23 years ago
|
||
Comment on attachment 122724 [details] [diff] [review]
Patch
a=sspitzer
Attachment #122724 -
Flags: approval1.4? → approval1.4+
|
|
Assignee | |
Comment 5•23 years ago
|
||
It's in
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
|
||
Updated•21 years ago
|
Product: Core → Other Applications
|
||
Updated•18 years ago
|
QA Contact: timeless → dom-inspector
You need to log in
before you can comment on or make changes to this bug.
Description
•