X
Thinta lapha ukuze uye kuveshini yamakhalekhukhwini kusayithi.

Isithangami Sabeseki

Lolu chungechunge lwabekwa kunqolobane. Uyacelwa ubuze umbuzo omusha uma udinga usizo.

HTML 5 videos (like Vine) won't play

Kuphostiwe

Some HTML5 videos won't play in my Firefox browser.

This vine for example (https://vine.co/v/b3v5h3Piwt7) only shows up as a static image. I can click the mute/audio button though, but it won't play. When I look at the webconsole when I load the page then 2 javascript warnings show up, the first one say that the Mediasource [long url here] can't be encoded and another one says loading of all candidate sources failed. loading media paused.

I'm using Firefox 21.0 and I tried to run Firefox in safe mode with disabled add-ons, and I also tried to reinstall it, but without success.

Thanks in advance.

Some HTML5 videos won't play in my Firefox browser. This vine for example (https://vine.co/v/b3v5h3Piwt7) only shows up as a static image. I can click the mute/audio button though, but it won't play. When I look at the webconsole when I load the page then 2 javascript warnings show up, the first one say that the Mediasource [long url here] can't be encoded and another one says loading of all candidate sources failed. loading media paused. I'm using Firefox 21.0 and I tried to run Firefox in safe mode with disabled add-ons, and I also tried to reinstall it, but without success. Thanks in advance.

Isisombululo esikhethiwe

You can try to set the media.windows-media-foundation.enabled pref to false on the about:config page to disable the built-in mp4 media player.

Funda le mpendulo ngokuhambisana nalesi sihloko 253

Eminye Imininingwane Yohlelo

Fakela amapulagi

  • Google Talk Plugin Video Accelerator version:0.1.44.29
  • Version 4.0.1.13525
  • 2.1.4
  • Shockwave Flash 11.7 r700
  • Google Update
  • NVIDIA 3D Vision plugin for Mozilla browsers
  • NVIDIA 3D Vision Streaming plugin for Mozilla browsers
  • Adobe PDF Plug-In For Firefox and Netscape 10.1.7
  • RealPlayer(tm) LiveConnect-Enabled Plug-In
  • RealPlayer Download Plugin
  • RealNetworks(tm) RealDownloader Chrome Background Extension Plug-In
  • RealNetworks(tm) RealDownloader PepperFlashVideoShim Plug-In
  • RealNetworks(tm) RealDownloader HTML5VideoShim Plug-In
  • RealDownloader Plugin
  • 2.1.3
  • Uplay PC Plugin
  • 0.3
  • A plugin to detect whether the Adobe Application Manager is installed on this machine.
  • 5.1.20125.0
  • Unity Player 4.0.1f2
  • Box Edit
  • Launches Gyre SoShare
  • Next Generation Java Plug-in 10.9.2 for Mozilla browsers
  • NPRuntime Script Plug-in Library for Java(TM) Deploy
  • RealNetworks(tm) RealPlayer Chrome Background Extension Plug-In
  • RealPlayer(tm) HTML5VideoShim Plug-In
  • The QuickTime Plugin allows you to view a wide variety of multimedia content in Web pages. For more information, visit the QuickTime Web site.
  • 0.70.4
  • The plug-in allows you to open and edit files using Microsoft Office applications
  • Office Authorization plug-in for NPAPI browsers

Isisebenziso

  • Firefox 21.0
  • Umsebenzisi oyi-ejenti: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:21.0) Gecko/20100101 Firefox/21.0
  • I-URL Yokweseka: http://support.mozilla.org/1/firefox/21.0/WINNT/nl/

Izandiso

  • Adblock Plus 2.2.4 ({d10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d})
  • Better Battlelog (BBLog) 3.5.3 (jid1-qQSMEVsYTOjgYA@jetpack)
  • Chat Undetected 0.91.61 (crossriderapp14917@crossrider.com)
  • ChatZilla 0.9.90 ({59c81df5-4b7a-477b-912d-4e0fdf64e5f2})
  • Dictionnaire français «Moderne» 4.3 (fr-moderne@dictionaries.addons.mozilla.org)
  • Dolphin Connect 0.6 (jid1-79nQAfjhUybb3A@jetpack)
  • DOM Inspector 2.0.14 (inspector@mozilla.org)
  • Firebug 1.11.4 (firebug@software.joehewitt.com)
  • goo.gl lite 1.8.1 (goo.gl_lite@matthew.flaschen.gatech.edu)
  • Greasemonkey 1.9 ({e4a8a97b-f2ed-450b-b12d-ee082ba24781})
  • InspectThis 1.0.0 (inspectthis@mackay.dyndns.info)
  • Lazarus: Form Recovery 2.3 (lazarus@interclue.com)
  • MEGA EXTENSION 1.0.3 (firefox@mega.co.nz)
  • OpenMedSpel 1.1.0 (openmedspel@e-medtools.com)
  • Personas Plus 1.7.2.1 (personas@christopher.beard)
  • Pocket 3.0.1 (isreaditlater@ideashower.com)
  • QuickProxy 2009.07.19 ({d5ea4520-61a1-11da-8cd6-0800200c9a66})
  • RealDownloader 1.3.1 ({DAC3F861-B30D-40dd-9166-F4E75327FAC7})
  • ReloadEvery 17.0.0 ({888d99e7-e8b5-46a3-851e-1ec45da1e644})
  • Troubleshooter 1.1a (troubleshooter@mozilla.org)
  • Twitter Address Bar Search 1 (twitter.address.bar.search@firefox.twitter)
  • PC Sync 2 Synchronisation Extension 1.0.0.756 (bkmrksync@nokia.com) (Akusebenzi)

I-Javascript

  • incrementalGCEnabled: True

Imidwebo

  • adapterDescription: NVIDIA GeForce GT 555M
  • adapterDescription2: Intel(R) HD Graphics 3000
  • adapterDeviceID: 0x0dcd
  • adapterDeviceID2: 0x0116
  • adapterDrivers: nvd3dumx,nvwgf2umx,nvwgf2umx nvd3dum,nvwgf2um,nvwgf2um
  • adapterDrivers2: igdumd64 igd10umd64 igd10umd64 igdumd32 igd10umd32 igd10umd32
  • adapterRAM: 3071
  • adapterRAM2: Unknown
  • adapterVendorID: 0x10de
  • adapterVendorID2: 0x8086
  • direct2DEnabled: True
  • directWriteEnabled: True
  • directWriteVersion: 6.2.9200.16492
  • driverDate: 5-12-2013
  • driverDate2: 3-19-2012
  • driverVersion: 9.18.13.2018
  • driverVersion2: 8.15.10.2696
  • info: {u'AzureCanvasBackend': u'direct2d', u'AzureFallbackCanvasBackend': u'cairo', u'AzureContentBackend': u'direct2d'}
  • isGPU2Active: False
  • numAcceleratedWindows: 2
  • numTotalWindows: 2
  • webglRenderer: Google Inc. -- ANGLE (NVIDIA GeForce GT 555M )
  • windowLayerManagerType: Direct3D 10

Okuthandwayo Okulungisiwe

  • accessibility.typeaheadfind: True
  • accessibility.typeaheadfind.flashBar: 0
  • browser.cache.disk.capacity: 358400
  • browser.cache.disk.smart_size.first_run: False
  • browser.cache.disk.smart_size.use_old_max: False
  • browser.cache.disk.smart_size_cached_value: 358400
  • browser.display.background_color: #C0C0C0
  • browser.display.use_system_colors: True
  • browser.history_expire_days.mirror: 20
  • browser.places.importBookmarksHTML: False
  • browser.places.smartBookmarksVersion: 4
  • browser.privatebrowsing.dont_prompt_on_enter: True
  • browser.search.useDBForOrder: True
  • browser.sessionstore.resume_from_crash: False
  • browser.startup.homepage: http://www.bungie.net/
  • browser.startup.homepage_override.buildID: 20130511120803
  • browser.startup.homepage_override.mstone: 21.0
  • browser.tabs.warnOnClose: False
  • dom.max_chrome_script_run_time: 0
  • dom.max_script_run_time: 0
  • dom.mozApps.used: True
  • dom.w3c_touch_events.expose: False
  • extensions.lastAppVersion: 21.0
  • general.useragent.extra.microsoftdotnet: ( .NET CLR 3.5.30729)
  • gfx.direct3d.prefer_10_1: True
  • network.cookie.prefsMigrated: True
  • network.protocol-handler.warn-external.dnupdate: False
  • places.database.lastMaintenance: 1370717245
  • places.history.expiration.transient_current_max_pages: 104858
  • places.history.expiration.transient_optimal_database_size: 167772160
  • places.last_vacuum: 1300912266
  • plugin.disable_full_page_plugin_for_types: application/pdf
  • privacy.cpd.downloads: False
  • privacy.cpd.formdata: False
  • privacy.cpd.history: False
  • privacy.cpd.offlineApps: True
  • privacy.cpd.sessions: False
  • privacy.donottrackheader.enabled: True
  • privacy.popups.showBrowserMessage: False
  • privacy.sanitize.migrateFx3Prefs: True
  • privacy.sanitize.timeSpan: 0
  • security.warn_viewing_mixed: False

Misc

  • Umsebenzisi JS: Yebo
  • Ukufinyeleleka: Cha
TrainerSteve 0 izisombululo 7 izimpendulo
Kuphostiwe

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.

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.

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. 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.

Okulungisiwe ngu TrainerSteve

nyet 0 izisombululo 10 izimpendulo
Kuphostiwe

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.

I am not interested in platform evangelization. I generally leave that to people who are clueless.

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. I am not interested in platform evangelization. I generally leave that to people who are clueless.
TrainerSteve 0 izisombululo 7 izimpendulo
Kuphostiwe

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.

Hopefully Mozilla will learn from it. But perhaps your screen name "nyet" says it all?

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. Hopefully Mozilla will learn from it. But perhaps your screen name "nyet" says it all?
nyet 0 izisombululo 10 izimpendulo
Kuphostiwe

"It is about competitive advantages in an extremely fluid web"

Meaningless marketing speak, having nothing to do with the underlying technologies, which depend on standards insuring interoperability.

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.

I agree that their suggestions for fixes were not good ones (especially the suggestion that people disable html5).

But ultimately, the fault lies with vine, who should have properly tested their JS on firefox in the first place.

Question: how did vine launch w/o testing this?

"It is about competitive advantages in an extremely fluid web" Meaningless marketing speak, having nothing to do with the underlying technologies, which depend on standards insuring interoperability. 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. I agree that their suggestions for fixes were not good ones (especially the suggestion that people disable html5). But ultimately, the fault lies with vine, who should have properly tested their JS on firefox in the first place. Question: how did vine launch w/o testing this?
nyet 0 izisombululo 10 izimpendulo
Kuphostiwe

Looks like vine fixed it on their end, finally.

Looks like vine fixed it on their end, finally.