http://support.mozilla.com/tiki-view_forum_thread.php?forumId=1&comments_parentId=29316#threadId39898 Make sure to include a link to Flash for people who have trouble viewing all Flash.
Summary: Can't view fullscreen Flash videos → KB article: Can't view fullscreen Flash videos
Written, ready for review
Assignee: nobody → bbayles
Status: NEW → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → FIXED
Pretty good! A few small changes: -I don't get a display tab when I go to settings on YouTube (Shockwave Flash 9.0 r47) -Can you explicitly say that if they have problems with all (non-fullscreen) Flash they should go to the Flash article? -Can you specifically mention YouTube as an example of a site that this could happen to? -Fullscreen is two words -Articles titles shouldn't have apostrophes (didn't think of this when naming the bug)
(1) Are you sure? Are you right-clicking the video (or any other Flash content) and clicking "Settings" from the context menu? Does yours not match my screenshot? The "Display" icon is not labeled except for in the header, as shown in the screenshot. (2) Done (3) I put youtube in the "tags" earlier, but I put it in the article now (4) Done (5) Done I'm using a different computer from my normal one this weekend, so I can't roll back Flash players to check (1).
Yeah, there's no tab for Display. It starts with Privacy.
If it's not there for older versions, maybe there should be a note to upgrade Flash? Or does this problem only occur with newer versions?
OK, I checked. The display tab is only accessible on newer versions. There was a forum post today with someone who had the problem on an older version. So, I made the first step "Update Flash." This is probably a good idea for everyone to do for security purposes anyway.
When an article is moved to the KB, remember to mark the bug as verified. Any further discussion about the article should take place on the staging copy <http://support.mozilla.com/kb/*Cannot+view+full+screen+Flash+videos>.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.