Closed Bug 1307862 Opened 8 years ago Closed 6 years ago

[e10s] "YouTube High Definition: version 49" video quality and size settings does not work in e10s

Categories

(Firefox :: Extension Compatibility, defect)

Product:
Firefox
Component:
Extension Compatibility
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED INVALID
Tracking Flags:
Tracking Status
platform-rel --- -

People

(Reporter: Abe_LV, Unassigned)

Details

(Whiteboard: [platform-rel-Youtube]) 

Steps to Reproduce:

1. Install Version 49.0 of the addon on e10s-enabled nightly/aurora: https://addons.mozilla.org/en-US/firefox/addon/youtube-high-definition/
2.Go to any youtube video
3. Click the addon from the toolbar for setting options
4. Select video quality /video size

Actual Result:

Dialog appears with the message “This is not a YouTube page. Would you like to open up a YouTube page to try the setting”

Expected Result:

User should be able to change settings in e10s enabled browser.

Note:
It is e10s specific. 
E10s enabled & interposition set to true/false - fails.
E10s disabled & interposition set to true/false - pass.
Flags: needinfo?(sescalante)
platform-rel: --- → ?
Whiteboard: [platform-rel-Youtube]
platform-rel: ? → -
Flags: needinfo?(sescalante)
Whiteboard: [platform-rel-Youtube] → [contact needed][platform-rel-Youtube]
Is this still happening in the latest version of the add-on (49.1)?
Flags: needinfo?(amasresha)
Yes, I can still reproduce it in Windows 10 with latest nightly.
Here is a screen capture: https://testing-1.tinytake.com/sf/MTEwMzI1Nl80Mzg1Njcx

--
Version 	52.0a1
Build ID 	20161106030203
Update Channel 	nightly
User Agent 	Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0
Flags: needinfo?(amasresha)
Thank you for testing!

The developer has been informed.
Whiteboard: [contact needed][platform-rel-Youtube] → [platform-rel-Youtube]
With Firefox 57, all add-ons are WebExtensions and e10s compatible.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.