Closed Bug 1399518 Opened 7 years ago Closed 7 years ago

Refactor BrowserApp-based window type detection

Categories

(GeckoView :: General, enhancement)

51 Branch
All
Android
enhancement
Not set
normal

Tracking

(firefox57 fixed)

RESOLVED FIXED
mozilla57
Tracking Status
firefox57 --- fixed

People

(Reporter: esawin, Assigned: esawin)

References

Details

Attachments

(1 file, 1 obsolete file)

In bug 1329154 we've added BrowserApp to the GeckoView window which breaks some modules that identify GeckoView windows by the absence of BrowserApp.
The windowtype should be a reliable way to detect GeckoView windows. Do we use this type of check anymore else?
Attachment #8907650 - Flags: review?(nchen)
Comment on attachment 8907650 [details] [diff] [review] 0001-Bug-1399518-1.0-Use-windowtype-to-detect-GeckoView-w.patch Review of attachment 8907650 [details] [diff] [review]: ----------------------------------------------------------------- What do you think about just checking for the feature? (e.g. `chromeWin.NativeWindow && chromeWin.NativeWindow.doorhanger`) So if we ever have a `NativeWindow.doorhanger` implementation for GeckoView we would use that automatically. ::: mobile/android/modules/Prompt.jsm @@ +23,5 @@ > .rootTreeItem.QueryInterface(Ci.nsIInterfaceRequestor) > .getInterface(Ci.nsIDOMWindow); > } > > +function isGeckoView(aWindow) { This feels a little backwards. I think it should be `isBrowserJS`, and we should compare against "navigator:browser".
Attachment #8907650 - Flags: review?(nchen) → review+
Pushed by esawin@mozilla.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/3a35599c5d1e [1.1] Check for NativeWindow features to identify the window type for prompt handling. r=jchen
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 57
Product: Firefox for Android → GeckoView
Target Milestone: Firefox 57 → mozilla57
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: