Pomoc pśepytaś

Glědajśo se wobšudy pomocy. Njenapominajomy was nigda, telefonowy numer zawołaś, SMS pósłaś abo wósobinske informacije pśeraźiś. Pšosym dajśo suspektnu aktiwitu z pomocu nastajenja „Znjewužywanje k wěsći daś“ k wěsći.

Learn More

YouTube HTML5 videos are choppy in Windows 10

  • 4 wótegrona
  • 18 ma toś ten problem
  • 18 naglědow
  • Slědne wótegrono wót kop48

more options

Disabling hardware acceleration addresses the issue. Does not repro if I play them in IE or Chrome on the same machine.

Disabling hardware acceleration addresses the issue. Does not repro if I play them in IE or Chrome on the same machine.

Wubrane rozwězanje

hi kop48, until windows 10 is still in an early pre-release state right now there might be all sorts of issues since drivers and software are not optimized yet. since there will still be lot of changes, i'm not sure if it would even be helpful to file a firefox bug at this stage...

Toś to wótegrono w konteksće cytaś 👍 1

Wšykne wótegrona (4)

more options

Wubrane rozwězanje

hi kop48, until windows 10 is still in an early pre-release state right now there might be all sorts of issues since drivers and software are not optimized yet. since there will still be lot of changes, i'm not sure if it would even be helpful to file a firefox bug at this stage...

more options

Actually, now is the perfect time to file bugs - that's the whole point of the Technical Preview!

more options

this might be the case for bugs filed against windows. however as long as the environment is still unstable and constantly changing (that's until windows 10 goes into release preview), it doesn't make sense for mozilla to invest resources to fix "bugs" that might go away anyway as the win10 development progresses further - an example for that would be bug #1089188...

more options

It makes sense for Mozilla to invest some time in an OS that many millions of people will be upgrading to, albeit I can understand having to wait until developer documentation is released so that Firefox devs can troubleshoot effectively. :)

Regardless, I've filed the bug with Microsoft - it might just be an Intel driver problem, as the issue isn't happening on my other machine with an NVidia GPU.