If plugins.click_to_play == true { if referr.plugins.playing == true { if referr.domain == this.domain { set this.plugins.playing := true; } } } Please automatically continue playing plugins on the condition when, you where playing the plugins on the page from where you came from and the current page and previous page are from the same domain. Navigation to new page may be by user action or by javascript. New page can be also be in new window/tab by window.open() or clicking on a link with target defined. Use case 1:- If a user want to watch all videos in a youtube playlist one after other automatically, it is not possible when plugins.click_to_play == true Steps:- 1. ensure about:config plugins.click_to_play == true 2. goto http://www.youtube.com/watch?v=HSHBCtZqK6s&playnext=1&list=PL1E742AC8A797C175 3. Click to activate plugin 4. Wait current/first video to finish 5. After completing current video, new video page has been show. Expected Result:- New video automatically starts. Current Result:- New video page shown with "Click to play again" Use case 2:- It is annoying to keep clicking, if a web site pages are made of flash contents Steps:- 1. ensure about:config plugins.click_to_play == true 2. goto http://www.starfall.com/n/level-k/index/play.htm 3. Page displayed with "Click to play" 4. Click to play, displays a flash app with alphabets on it 5. Click letter "A" on the page content 6. Page speedily with "Click to play" 7. Click to play, displays a flash content 8. Click exit [ X ] button 9. Page displayed with "Click to play" 10. this goes on Expected Result:- every time on new page video start automatically. Use case 3:- You are on a shopping site and flash video is shown on a pop-up window, when click a demo button on the item list.

What do you think about the user being able to 'always enable plugins for this domain' instead for a site that relies heavily on plugin content on different pages that the user trusts ?

(In reply to Ian Melven :imelven from comment #1) > What do you think about the user being able to 'always enable plugins for > this domain' instead for a site that relies heavily on plugin content on > different pages that the user trusts ? Yes that will be great for many sites http://pbskids.org/go/ http://www.starfall.com/ BUT... 1. assume I visit porn sites in "Private Browsing Mode", also assume the plug-in-s totally support "Private Browsing Mode" I wont be able to use the per site option. 2. Another case I go to * http://www.thedailyshow.com/full-episodes/ * http://www.cnn.com/video/ * http://www.youtube.com/user/CNN to check whether for `new video` or `video I am interested in` If auto play is enabled on these sites, (say for continue auto-playing playlist) the video start playing, sucking my internet bandwidth and device resource, even though I only want to see just the description of the video. So instead of just plugins.click_to_play = true/FALSE option I like to see an option with plugins.play - 1. click_to_play on every page visit - 2. shipped as DEFAULT enable auto play once user click_to_play for the window for the same site/domain in that session - 3. auto play on all websites

for option 1 may be further divided in to 1.a play only the plugin I clicked 1.b play all the plugins on the page when I click see attachment 616429 [details]

Commit pushed to master at https://github.com/mozilla/mozillians https://github.com/mozilla/mozillians/commit/bee01e95b3b12a21d5a11fa43b31d9b3be454e28 [Fix bug747312] Strip trailing slashes in urls - r=jsocol - Permanent redirect from /en-US/foo/ to /en-US/foo - Moves middleware to common app - Adds middleware test - Clean up URLs - Fix bug 747413

This bug wasn't actually fixed. It looks like someone had a typo in their commit message.

The playlist use case makes sense. > What do you think about the user being able to 'always enable plugins for > this domain' instead for a site that relies heavily on plugin content on > different pages that the user trusts ? But I would never choose this. I don't want to tell Firefox to auto-play all YouTube videos. I only agree for auto-playing videos in a playlist, except the first one.

(In reply to Biju from comment #0) > Please automatically continue playing plugins on the condition when, > you where playing the plugins on the page from where you came from > and the current page and previous page are from the same domain. This will be resolved by the new click-to-play behaviour as per the UI spec. The default "allow" action will result in the plugin staying activated until the user wasn't actively using the page for some time. Also there will be an option for longer-term activation.

I am lost after reading https://wiki.mozilla.org/Opt-in_activation_for_plugins Let me know the relevant portion of the UI spec which you think solve my need. I think if there is a per-site-option the issue I face will be partially solved. Actually I need a per-site-option-pugin-enable = ask-once-for-session. Original issue was, a firefox install of one of my friends PC was crashing multiple times a day. We removed the user profile and reinstalled firefox, still there was crashing. We tried disabling the Flash, and that did help. Now you totally lost good things of Flash, ie watching videos So I told him this new about:config plugins.click_to_play == true He did it and it was great till his kids want to play game at http://pbskids.org/ Each time they have to do click to go. Also it was terrible when playing you tube video play list with autonext

(In reply to Biju from comment #8) > I am lost after reading > https://wiki.mozilla.org/Opt-in_activation_for_plugins > Let me know the relevant portion of the UI spec which you think solve my > need. This was an earlier phase, since then the UX was getting a redesign. The discussion is currently on the firefox-dev mailing list, the latest spec version that i was referring to in comment 7 can be found here: http://people.mozilla.org/~lco/CtP/current/

(In reply to Georg Fritzsche [:gfritzsche] from comment #9) > http://people.mozilla.org/~lco/CtP/current/ I think it will solve my issue as it have pre-site option.

This was fixed by bug 880735 and it's dependencies.