Closed Bug 1324899 Opened 8 years ago Closed 8 years ago

Port bug 1322414 (remove content-primary) to DOM Inspector

Categories

(Other Applications :: DOM Inspector, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: frg, Assigned: frg)

References

Details

Attachments

(1 file, 2 obsolete files)

DOMi has a content-primary in resources\content\inspectorOverlay.xul. Bug 1322414 basically changed this to type="content" primary="true". This needs to be ported to the current DOMi for SeaMonkey 2.50+ and any gecko 53+ application.
Attached patch 1324899-DOMiContentPrimary.patch (obsolete) — Splinter Review
Changing content-primary and adjusting min version numbers. Setting version to 2.0.18.0 so that it updates when bundled with SeaMonkey. Not taking the bug yet. I am unhappy with the patch because this would make it incompatible with older versions and PM. Maybe type and primary can be set depending on version number?
Attachment #8820410 - Flags: feedback?(philip.chee)
This does it for me and preserves compatibility. Tested with SeaMonkey 2.50a1 and 2.49a2.
Assignee: nobody → frgrahl
Attachment #8820410 - Attachment is obsolete: true
Status: NEW → ASSIGNED
Attachment #8820410 - Flags: feedback?(philip.chee)
Attachment #8820736 - Flags: review?(philip.chee)
Ian, can you put up a new version on AMO? Instead of 2.0.18.0 I am thinking of 2.0.17.0. Rationale for the last minor version is the same as for debugQA. If it changes it will autoupdate when bundled with a Nightly Seamonkey.
Flags: needinfo?(iann_bugzilla)
(In reply to Frank-Rainer Grahl from comment #3) Also see "Bug 1324196 - DOM Inspector 2.0.16.1-signed only compatible until SeaMonkey 2.39"
See Also: → 1324196
(In reply to Frank-Rainer Grahl from comment #3) > Ian, > > can you put up a new version on AMO? Instead of 2.0.18.0 I am thinking of > 2.0.17.0. Rationale for the last minor version is the same as for debugQA. > If it changes it will autoupdate when bundled with a Nightly Seamonkey. That would be mcsmurf, ewong, callek or KaiRo I think.
Flags: needinfo?(iann_bugzilla)
Comment on attachment 8820736 [details] [diff] [review] 1324899-DOMiContentPrimary-V2.patch > + if (Services.vc.compare(Services.appinfo.platformVersion, "53.0a1") < 0) { > + let ifBrowser = document.getElementById("ifBrowser"); > + ifBrowser.removeAttribute("primary"); > + ifBrowser.setAttribute("type", "content-primary"); No need to remove "primary" attribute since it means nothing for Gecko < 53 Hence we can simplify: document.getElementById("ifBrowser").setAttribute("type", "content-primary"); For uploading to AMO please ask mcsmurf.
Attachment #8820736 - Flags: review?(philip.chee) → review+
Fixed Patch. Tested with 2.48 and 2.50a1. Current DOMi on AMO is 2.0.16.1 so I put 2.0.17.0 in the patch. Review+ from Philip Chee carried forward.
Attachment #8820736 - Attachment is obsolete: true
Attachment #8822941 - Flags: review+
https://hg.mozilla.org/dom-inspector/rev/a69769cacd8dbf7b2d41ff361c25d3712c72355d If you installed the 2.0.18.0 xpi from the previous patch please install the 2.0.17.0 xpi manually again.
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Target Milestone: --- → 2.0
Callek, die you find the AMO password and could you give it to a council member?
Flags: needinfo?(bugspam.Callek)
(In reply to Frank-Rainer Grahl from comment #9) > Callek, > > die you find the AMO password and could you give it to a council member? I did not find it yet, will leave the n-i open so I can try and squeeze looking into my agenda this week.
Flags: needinfo?(bugspam.Callek)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: