Các câu trả lời gần đây cho HTML 5 videos (like Vine) won't playhttps://support.mozilla.org/vi/questions/9616272013-11-29T06:12:05-08:00Looks like vine fixed it on their end, finally.
2013-11-29T06:12:05-08:00nyethttps://support.mozilla.org/vi/questions/961627?page=3#answer-506751<p>Looks like vine fixed it on their end, finally.
</p>"It is about competitive advantages in an extremely fluid web"
Meaningless marketing speak, having n2013-11-03T05:33:25-08:00nyethttps://support.mozilla.org/vi/questions/961627?page=3#answer-497065<p>"It is about competitive advantages in an extremely fluid web"
</p><p>Meaningless marketing speak, having nothing to do with the underlying technologies, which depend on standards insuring interoperability.
</p><p>The fundamental source of the problem is Vine's source code. Period. That is where the bug lies. Whether or not Mozilla should have added a workaround (sooner) isn't really relevant, especially if the workaround has unintended side effects in the JS interpreter, which cause other issues.
</p><p>I agree that their suggestions for fixes were not good ones (especially the suggestion that people disable html5).
</p><p>But ultimately, the fault lies with vine, who should have properly tested their JS on firefox in the first place.
</p><p>Question: how did vine launch w/o testing this?
</p>This isn't about platform evangelism. It is about competitive advantages in an extremely fluid web.2013-11-03T05:28:12-08:00TrainerStevehttps://support.mozilla.org/vi/questions/961627?page=3#answer-497064<p>This isn't about platform evangelism. It is about competitive advantages in an extremely fluid web. That Mozilla took so long to fix a basic problem with playing Twitter's Vines, an extremely popular web app, is disturbing. That one had to resort to using an alternative browser in the interim, just to view one's own Vines, is really, really sad.
</p><p>Hopefully Mozilla will learn from it. But perhaps your screen name "nyet" says it all?
</p>Shrug. Thats the way programming works. Bugs in the source can have different results depending on t2013-11-03T05:18:51-08:00nyethttps://support.mozilla.org/vi/questions/961627?page=3#answer-497060<p>Shrug. Thats the way programming works. Bugs in the source can have different results depending on the compiler/interpreter. The proper fix (according to the JS standard) is in the git hub commit I posted. This is not a matter of opinion, this is fact.
</p><p>I am not interested in platform evangelization. I generally leave that to people who are clueless.
</p>I did read the whole thread. All sorts of "fixes" were proposed, most involving hacking into the Sy2013-11-03T05:15:43-08:00TrainerStevehttps://support.mozilla.org/vi/questions/961627?page=3#answer-497058<p>I did read the whole thread. All sorts of "fixes" were proposed, most involving hacking into the System by the User. And what a terrible shame that the Mozilla Team could not come up with and deploy a "workaround for the bug" for some 4 or 5 months, while all the other browser makers had the fix for Vine from Day 1.
</p><p>One would think that the Mozilla team would be way ahead of the competition, not months behind. Just saying, someone at Mozilla needed to get on top of this one with a permanent fix, and not continue to deny it while trying to get Users to fix it for them. A little constructive criticism should not be ignored taken as a personal insult. If you want to be the default browser, you need to be better than the competition. Otherwise you will go the way of all the other abandoned browsers since 1992. RIP Nexus, Voila, Mosaic, Cello, Arena, Netscape, etc.
</p>Read the whole thread. The source of the bug is bad javascript. This sort of thing is very common; s2013-11-03T05:00:07-08:00nyethttps://support.mozilla.org/vi/questions/961627?page=2#answer-497051<p>Read the whole thread. The source of the bug is bad javascript. This sort of thing is very common; some implementations of the js interpreter react differently to bugs in the source.
</p><p>As I posted above, the true fix is here:
</p><p><a href="https://github.com/heff/video-js/commit/1d82ea7d2aa075e5f4990574378c15207c30dc4f" rel="nofollow">https://github.com/heff/video-js/commit/1d82ea7d2aa075e5f4990574378c15207c30dc4f</a>
</p><p>Just because there is a js interpreter side workaround for the bug does not mean the bug isn't in the source.
</p>Oh Really? A "bug in Vine's javascript" that ONLY affected Firefox and Seamonkey? All other browse2013-11-03T03:27:46-08:00TrainerStevehttps://support.mozilla.org/vi/questions/961627?page=2#answer-497026<p>Oh Really? A "bug in Vine's javascript" that ONLY affected Firefox and Seamonkey? All other browsers had no such issue - Chrome, Safari, and even IE had no problem playing Vines. Only Firefox and Seamonkey had the problem. And the problem only went away with the latest releases of the two. How fascinating.
</p>Because it wasn't a mozilla bug. It was a bug in vine's javascript.
2013-11-03T03:07:02-08:00nyethttps://support.mozilla.org/vi/questions/961627?page=2#answer-497020<p>Because it wasn't a mozilla bug. It was a bug in vine's javascript.
</p>Can verify that it finally also works for me in Firefox 26 beta 1 (Vista 32 platform), and in Seamon2013-11-02T21:41:06-07:00TrainerStevehttps://support.mozilla.org/vi/questions/961627?page=2#answer-496891<p>Can verify that it finally also works for me in Firefox 26 beta 1 (Vista 32 platform), and in Seamonkey 2.21 and 2.22 - without tampering with security settings, config files, of embedding anything. Just click and it plays. Problem finally solved for me.
</p><p>But why did it take so long to solve such a basic problem??? Months and months this has been a complaint. Was it complete denial and laziness at the code writing and working level, combined with a random choice to try to get Users to fix a bug in the code by screwing around with their sensitive MS config file and security settings? When all the other non-Mozilla browsers worked just fine without user tampering? Really? C'mon!
</p>Just found another way of loading vines defiantly works on ver. 25. If you click the embed button it2013-10-30T00:05:04-07:00Tomgeekhttps://support.mozilla.org/vi/questions/961627?page=2#answer-495395<p>Just found another way of loading vines defiantly works on ver. 25. If you click the embed button it will give you some copy and paste code but also a preview window that works perfectly.
</p>Hi Tomgeek, that's a great discovery. It seems when I view the /card page Firefox doesn't resize the2013-10-27T02:46:33-07:00jscher2000https://support.mozilla.org/vi/questions/961627?page=2#answer-494239<p>Hi Tomgeek, that's a great discovery. It seems when I view the /card page Firefox doesn't resize the video, so to see the example, I used full screen (F11 to enter and exit). Not sure if this is a setting I have or an issue with the page.
</p>An easy way of doing it manually while still maintaining HTML5 support, is to add /card at the end o2013-10-26T06:51:38-07:00Tomgeekhttps://support.mozilla.org/vi/questions/961627?page=2#answer-494036<p>An easy way of doing it manually while still maintaining HTML5 support, is to add /card at the end of the web addresses. ie <a href="https://vine.co/v/hpPHmntzMjY" rel="nofollow">https://vine.co/v/hpPHmntzMjY</a> doesn't work. But <a href="https://vine.co/v/hpPHmntzMjY/card" rel="nofollow">https://vine.co/v/hpPHmntzMjY/card</a> does.&nbsp;:)
</p>Unfortunately, it doesn't seem that vine has any intention of fixing their js.
2013-10-22T15:43:02-07:00nyethttps://support.mozilla.org/vi/questions/961627?page=2#answer-492782<p>Unfortunately, it doesn't seem that vine has any intention of fixing their js.
</p>On the 3 Vine pages I saw linked in this thread, the necessary information is in the document, so yo2013-10-10T14:24:57-07:00jscher2000https://support.mozilla.org/vi/questions/961627?page=2#answer-488527<p>On the 3 Vine pages I saw linked in this thread, the necessary information is in the document, so you can use a bookmarklet to fix the broken video tag. For those of you unfamiliar with the term, a bookmarklet is a script you run by clicking a bookmark, typically on your Bookmarks Toolbar.
</p><p>I posted a sample button on this page for testing: <a href="http://dev.jeffersonscher.com/bookmarklets.html#vinevids" rel="nofollow">http://dev.jeffersonscher.com/bookmarklets.html</a>
</p><p>When you see the video isn't working, click the button and the script fills in the missing information and the video should play.
</p><p>Note #1: I tested on Windows 7 with MPEG support enabled.
</p><p>Note #2: The tags in the pages I tested all referenced Twitter, so I used that exact information. If Vine is used for other sites, the bookmarklet may not work in those pages. Please post example URLs and I'll see whether I can generalize the bookmarklet to work there, too.
</p><p>Well, maybe it's better than nothing.
</p>Fix is apparently in github.
https://github.com/heff/video-js/commit/1d82ea7d2aa075e5f4990574378c1522013-10-10T13:17:21-07:00nyethttps://support.mozilla.org/vi/questions/961627?page=2#answer-488510<p>Fix is apparently in github.
</p><p><a href="https://github.com/heff/video-js/commit/1d82ea7d2aa075e5f4990574378c15207c30dc4f" rel="nofollow">https://github.com/heff/video-js/commit/1d82ea7d2aa075e5f4990574378c15207c30dc4f</a>
</p><p>Unclear why vine doesn't seem terribly concerned about the fact that their entire site is useless in firefox
</p>Actual useful information about this bug is here:
https://bugzilla.mozilla.org/show_bug.cgi?id=881072013-09-29T08:41:31-07:00nyethttps://support.mozilla.org/vi/questions/961627?page=2#answer-484541<p>Actual useful information about this bug is here:
</p><p><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=881072" rel="nofollow">https://bugzilla.mozilla.org/show_bug.cgi?id=881072</a>
</p><p>Seems as though the src attribute on the vine embedded video object is not being set properly by the js interpreter
</p>Disabling embedded html5 video is NOT a solution.
http://userscripts.org/scripts/review/176997
2013-09-29T08:37:50-07:00nyethttps://support.mozilla.org/vi/questions/961627?page=2#answer-484538<p>Disabling embedded html5 video is NOT a solution.
</p><p><a href="http://userscripts.org/scripts/review/176997" rel="nofollow">http://userscripts.org/scripts/review/176997</a>
</p>I don't understand why this is ONLY a problem for FireFox and SeaMonkey, and that nobody is recogniz2013-08-25T19:22:07-07:00TrainerStevehttps://support.mozilla.org/vi/questions/961627?page=2#answer-472956<p>I don't understand why this is ONLY a problem for FireFox and SeaMonkey, and that nobody is recognizing that it is a Mozilla thing, not a System thing.
</p><p>All the other browsers I have (Chrome, IE, Safari) have NO ISSUES with playing vines without having to make changes to the system configuration file.
</p><p>This sort of idiocy makes me want to drop Firefox as my preferred browser, and just get rid of it, while morons continue to suggest that I hack into my security settings, rather than FIXING THE BUG IN FIREFOX.
</p><p>And yes, it is still there in v. 24.0, both the beta and official release.
</p><p>By the way, I dug my old Win-XP SP3 laptop out of the graveyard, loaded the latest Firefox, and that antique plays vines just fine. So again, it is a problem specifically with FF under Win-Vista (and maybe other more recent Windows).
</p>this "fix" just caused a world of other problems. going the about:config route. ruins twitter homepa2013-08-25T14:05:21-07:00frostythepoptarthttps://support.mozilla.org/vi/questions/961627?page=2#answer-472887<p>this "fix" just caused a world of other problems. going the about:config route. ruins twitter homepage where it loads incorrectly. we need a real fix to this vine issue.
</p>If you make the fix that you suggested, it may compromise the security of your system. I'm not sugge2013-08-25T00:35:29-07:00musicn1957https://support.mozilla.org/vi/questions/961627?page=2#answer-472603<p>If you make the fix that you suggested, it may compromise the security of your system. I'm not suggesting that for my students because I don't want them to potentially be exposed to a risk.
</p>