Closed Bug 1403445 Opened 8 years ago Closed 7 years ago

Add better UI indicators that cookie settings were changed from the default.

Categories

(Firefox :: Site Identity, defect, P3)

52 Branch
defect

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: epistemepromeneur, Unassigned)

Details

(Whiteboard: [summary in comment 11])

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0 Build ID: 20170807000000 Steps to reproduce: i read a page. in this page there is a rectangle to display a video. i get a black rectangle instead of video. see http://www.lemonde.fr/disparitions/article/2017/09/26/le-chanteur-gerard-palaprat-est-mort_5191591_3382.html or http://videos.leparisien.fr/video/des-navettes-sans-chauffeurs-roulent-a-rungis-25-09-2017-x61xl4n if i select "display this frame only" then i can see the video. with all modules inactivated then same problem.
Component: Untriaged → Audio/Video: Playback
Product: Firefox → Core
(In reply to promeneur from comment #0) > with all modules inactivated then same problem. Your system doesn't appear to support AAC and/or H.264. You can confirm this by looking at https://www.youtube.com/html5
Flags: needinfo?(epistemepromeneur)
i made a test at https://www.youtube.com/html5 FF is completely compliant i assume FF uses gstreamer. i checked that i can play mp4 video with dragon player or vlc. all of them use gstreamer. libfaac0, libfaad2 are installed.
you read badly the description "if i select "display this frame only" then i can see the video."
Flags: needinfo?(epistemepromeneur)
(In reply to promeneur from comment #2) > i assume FF uses gstreamer. i checked that i can play mp4 video with dragon > player or vlc. all of them use gstreamer. Firefox does not use gstreamer. (In reply to promeneur from comment #3) > you read badly the description > > "if i select "display this frame only" then i can see the video." Sorry, my mistake. I can't reproduce the issue in 52 or 58 on Linux. Can you try safe mode https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode What Linux distro are you using?
as i said in description "with all modules inactivated then same problem." i found it. i must set to "always" "i accept third party cookies" to play video. in the url address field in the "i" menu we need an option to switch between "never", "from visited" and "always". thanks
Component: Audio/Video: Playback → Site Identity and Permission Panels
Flags: needinfo?(ajones)
Product: Core → Firefox
Summary: black rectangle instead of video displayed in its frame → Improve cookie UI
:k17e, can you please elaborate on what "Improve cookie UI" is supposed to mean and then also update the bug title to be more specific? In it's current state this bug looks slated to be closed as INCOMPLETE. Thank you.
(In reply to Johann Hofmann [:johannh] from comment #6) > :k17e, can you please elaborate on what "Improve cookie UI" is supposed to > mean and then also update the bug title to be more specific? In it's current > state this bug looks slated to be closed as INCOMPLETE. > > Thank you. please read carefully the "description" of the problem and the solution i found in comment #5 "in the url address field in the "i" menu we need an option to switch between "never", "from visited" and "always"." for parameter "accept tiers cookie".
Summary: Improve cookie UI → [enhancement] in the url address field in the "i" menu we need an option to switch between "never", "from visited" and "always"." for parameter "accept tiers cookie"
(In reply to promeneur from comment #7) > (In reply to Johann Hofmann [:johannh] from comment #6) > > :k17e, can you please elaborate on what "Improve cookie UI" is supposed to > > mean and then also update the bug title to be more specific? In it's current > > state this bug looks slated to be closed as INCOMPLETE. > > > > Thank you. > > please read carefully the "description" of the problem and the solution i > found in comment #5 > > "in the url address field in the "i" menu we need an option to switch > between "never", "from visited" and "always"." for parameter "accept tiers > cookie". So, just that I understand this correctly, you changed a global cookie setting in preferences, causing a badly written site to break, and now you'd like to expose this setting somewhere else in Firefox UI? I don't think that's a course of action I'd like to support.
(In reply to Johann Hofmann [:johannh] from comment #8) > So, just that I understand this correctly, you changed a global cookie > setting in preferences, causing a badly written site to break, and now you'd > like to expose this setting somewhere else in Firefox UI? I don't think > that's a course of action I'd like to support. i don't understand your answer. - year after year password manager is adapted to badly written login procedure site - if i inactivate flashplayer there is a button to manage activate/inactivate state for site using flashplayer. - if i choose "no track" i have an option in the menu "locker" to manage this parameter my wish does not seem extraordinary.
(In reply to promeneur from comment #9) > (In reply to Johann Hofmann [:johannh] from comment #8) > > > So, just that I understand this correctly, you changed a global cookie > > setting in preferences, causing a badly written site to break, and now you'd > > like to expose this setting somewhere else in Firefox UI? I don't think > > that's a course of action I'd like to support. > > i don't understand your answer. > > - year after year password manager is adapted to badly written login > procedure site > - if i inactivate flashplayer there is a button to manage > activate/inactivate state for site using flashplayer. > - if i choose "no track" i have an option in the menu "locker" to manage > this parameter > > my wish does not seem extraordinary. You can use the page info window to manage cookie settings for specific websites (Tools -> Page Info). Global settings are not exposed in the site identity panel, because that panel is specific to the site you're currently viewing. I concede that there are problems around communicating the fact that cookie settings might cause this website to malfunction, which is especially relevant since I believe we'd like to roll out experiments that change these settings by default.
To summarize ... To make embedded dailymotion.com videos play with network.cookieBehavior=1, one must: 1. Visit www.dailymotion.com 2. Open Tools -> Page Info 3. Select "Permissions" 4. Scroll down to "Set Cookies" 5. Un-check "Use default" A UI experiment to make this process smoother could be a privacy warning modal on top of the iframe element. (Like DuckDuckGo does before it plays videos in Private Browsing windows) ... "Dailymotion does not let you watch videos anonymously. As such, watching Dailymotion videos here will be tracked by Dailymotion. [Watch Here] [Watch on Dailymotion]" [Watch Here] - allow Dailymotion to set cookies (temporarily?), reload the iframe element, (delete the cookies set by Dailymotion?) [Watch on Dailymotion] - open the embedded element in a new tab (cookies will be first party)
Leaving this in Site Identity because I can't really think of a better component right now. Feel free to move if you do.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Priority: -- → P3
Summary: [enhancement] in the url address field in the "i" menu we need an option to switch between "never", "from visited" and "always"." for parameter "accept tiers cookie" → Add better UI indicators that cookie settings were changed from the default.
Whiteboard: [summary in comment 11]
(In reply to Johann Hofmann [:johannh] from comment #6) > :k17e, can you please elaborate on what "Improve cookie UI" is supposed to > mean and then also update the bug title to be more specific? In it's current > state this bug looks slated to be closed as INCOMPLETE. Sorry about such a poor description. I don't recall what I was thinking at the time other than making it easier for users to diagnose this kind of problem.
Flags: needinfo?(ajones)

This has sort of happened with the new content blocking UI...

Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.