The default bug view has changed. See this FAQ.

Port |Bug 752461 - First time after choosing to "Never activate plugins for this site" the video is still playing|

RESOLVED FIXED in seamonkey2.18

Status

SeaMonkey
General
RESOLVED FIXED
5 years ago
4 years ago

People

(Reporter: mcsmurf, Assigned: Philip Chee)

Tracking

Trunk
seamonkey2.18

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment, 1 obsolete attachment)

(Reporter)

Description

5 years ago
STR:
1. Make sure plugins.click_to_play pref is set on TRUE in about:config
2. Open http://www.youtube.com/
3. Click on a video
4. Click on the plugin icon in the location bar
5. Choose to "Never activate plugins for this site"
6. Click on the video screen

Expected results:
The video should not play (or hide the click-to-play UI altogether)

Actual results:
The video starts playing
(Reporter)

Comment 1

4 years ago
Fixing this bug will fix test13b in suite/browser/test/browser/browser_pluginnotification.js
(Assignee)

Comment 2

4 years ago
Created attachment 696063 [details] [diff] [review]
Patch v1.0 Proposed fix.

> Fixing this bug will fix test13b in suite/browser/test/browser/browser_pluginnotification.js
This seems to work.
Assignee: nobody → philip.chee
Status: NEW → ASSIGNED
Attachment #696063 - Flags: review?(bugzilla)
(Reporter)

Comment 3

4 years ago
Comment on attachment 696063 [details] [diff] [review]
Patch v1.0 Proposed fix.

Per IRC this is the wrong patch, Philip will attach a new one.
Attachment #696063 - Flags: review?(bugzilla)
(Assignee)

Comment 4

4 years ago
Created attachment 701830 [details] [diff] [review]
Patch v1.1

I can't get the tests to work. Frank, any ideas?

INFO TEST-START | Shutdown
Browser Chrome Test Summary
        Passed: 16
        Failed: 6
        Todo: 0

INFO | runtests.py | Running tests: end.
mochitest-browser-chrome failed:
TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/suite/browser/test/browser_pluginnotification.js | Test 3, plugin fallback type should be PLUGIN_DISABLED - Got 1, expected 2
TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/suite/browser/test/browser_pluginnotification.js | Test 3, found 'manage' link in plugin-problem binding
TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/suite/browser/test/browser_pluginnotification.js | uncaught exception - TypeError: aTarget is null at chrome://mochikit/content/tests/SimpleTest/EventUtils.js:276
TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/suite/browser/test/browser_pluginnotification.js | Test timed out
TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/suite/browser/test/browser_pluginnotification.js | Found a tab after previous test timed out: chrome://mochitests/content/browser/suite/browser/test/plugin_test.html
TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/suite/browser/test/browser_pluginnotification.js | uncaught exception - ReferenceError: executeSoon is not defined at chrome://mochitests/content/browser/suite/browser/test/browser_pluginnotification.js:88
c:\t1\hg\comm-central\suite\build.mk:78:0: command 'errors=`grep "TEST-UNEXPECTED-" mochitest-browser-chrome.log` ; if test "$errors" ; then echo "mochitest-browser-chrome failed:"; echo "$errors";  exit 1; fi' failed, return code 1
c:\t1\hg\objdir-sm\Makefile:52:0: command 'c:/DEV/mozilla-build/python/python.exe c:/t1/hg/comm-central/mozilla/build/pymake/pymake/../make.py -C mozilla mochitest-browser-chrome' failed, return code 2
Attachment #696063 - Attachment is obsolete: true
Attachment #701830 - Flags: feedback?(bugzilla)
(Reporter)

Comment 5

4 years ago
Philip: Did you only run the browser_pluginnotification.js test or the whole mochitest-browser-chrome test suite? Just wondering as for me only test12c and test18e fail with your patch applied (those two tests also fail without your patch).
(Assignee)

Comment 6

4 years ago
Comment on attachment 701830 [details] [diff] [review]
Patch v1.1

> Philip: Did you only run the browser_pluginnotification.js test or the whole
> mochitest-browser-chrome test suite? Just wondering as for me only test12c and

I only ran browser_pluginnotification.js.

> test18e fail with your patch applied (those two tests also fail without your
> patch)

Hmm. must be something local to me then. If only two tests fail for you with or without my patch I think it should be OK.

Switching f? to r?
Attachment #701830 - Flags: feedback?(bugzilla) → review?(bugzilla)
(Reporter)

Comment 7

4 years ago
Comment on attachment 701830 [details] [diff] [review]
Patch v1.1

r+, but add a semicolon here:

+            var doc = this.activeBrowser.contentWindow.document

(though the code also works without the semicolon).
Attachment #701830 - Flags: review?(bugzilla) → review+
(Assignee)

Comment 8

4 years ago
Pushed to comm-central:
http://hg.mozilla.org/comm-central/rev/d974df0945d3
Status: ASSIGNED → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → seamonkey2.18

Updated

4 years ago
Depends on: 860537
You need to log in before you can comment on or make changes to this bug.