Good [was 'bad'] news about Firefox and HTML5 standalones

Bringing your stacks to the web

Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller, robinmiller

Post Reply
[-hh]
VIP Livecode Opensource Backer
VIP Livecode Opensource Backer
Posts: 2262
Joined: Thu Feb 28, 2013 11:52 pm
Location: Göttingen, DE

Good [was 'bad'] news about Firefox and HTML5 standalones

Post by [-hh] » Tue Jan 26, 2016 9:25 pm

 
The latest Firefox version (44.0) doesn't support our HTML5 standalones any more!

I noticed this already the day before yesterday in the FirefoxDeveloperEdition and wrote a (presumably unread) 'urgent report' about that.

Firefox! Oh no, no! Until now by far the best with caching and running our HTML5 standalones.

I tried without any success:
= using it not via local file but via a web server,
= using no async in the js-script loading,
= turning off hardware acceleration,
= turning off 'multiprocesses' support.

Who knows what's going on?

It is NOT the new Chromium I believe.
Google Chrome with an even more advanced Chromium works fine.
[Safari and Opera also work, Microsoft's products not (we know)].
Last edited by [-hh] on Tue Feb 23, 2016 12:35 am, edited 1 time in total.
shiftLock happens

peter-b
Posts: 182
Joined: Thu Nov 20, 2014 2:14 pm
Location: LiveCode Ltd.

Re: Bad news about Firefox and HTML5 standalones

Post by peter-b » Wed Jan 27, 2016 11:00 am

Hi Hermann,

I have checked through all of the open HTML5-related bug reports in the bug tracker, and I cannot see it! Maybe the report submission did not go through properly? Did you get an e-mail confirming that the bug report was created?

Peter
LiveCode Open Source Team — @PeterTBBrett — peter.brett@livecode.com

[-hh]
VIP Livecode Opensource Backer
VIP Livecode Opensource Backer
Posts: 2262
Joined: Thu Feb 28, 2013 11:52 pm
Location: Göttingen, DE

Re: Bad news about Firefox and HTML5 standalones

Post by [-hh] » Wed Jan 27, 2016 11:36 am

Hi Peter,

misunderstanding here.
I didn't report it to LC-Bugs because I saw it first in the FirefoxDeveloperEdition and I didn't judge this to be a LC-Bug!

The report was to the Firefox developers team. They ask for reports, because they are changing a lot with regards to serve multiprocesses and they also think about supporting Google's new image format webP.

Can you solve this? Or tell us what we could do to have Firefox back for the HTML5 standalones?

Hermann
shiftLock happens

peter-b
Posts: 182
Joined: Thu Nov 20, 2014 2:14 pm
Location: LiveCode Ltd.

Re: Bad news about Firefox and HTML5 standalones

Post by peter-b » Wed Jan 27, 2016 11:37 am

I can't necessarily solve this if it's something that's been changed in Firefox upstream! But I'd really appreciate a link to the bug report in the Firefox bug tracker, please!
LiveCode Open Source Team — @PeterTBBrett — peter.brett@livecode.com

[-hh]
VIP Livecode Opensource Backer
VIP Livecode Opensource Backer
Posts: 2262
Joined: Thu Feb 28, 2013 11:52 pm
Location: Göttingen, DE

Re: Bad news about Firefox and HTML5 standalones

Post by [-hh] » Wed Jan 27, 2016 11:45 am

Wasn't a "bug-report".
If you switch the 'use multiprocesses' on/off in the FirefixDeveloperEdition they ask for a report with a mailing form. I thought this was related to that feature and reported. So I don't even have a copy of that sorry.
shiftLock happens

peter-b
Posts: 182
Joined: Thu Nov 20, 2014 2:14 pm
Location: LiveCode Ltd.

Re: Bad news about Firefox and HTML5 standalones

Post by peter-b » Wed Jan 27, 2016 11:45 am

Oh well, never mind! I will look out for the issue.
LiveCode Open Source Team — @PeterTBBrett — peter.brett@livecode.com

[-hh]
VIP Livecode Opensource Backer
VIP Livecode Opensource Backer
Posts: 2262
Joined: Thu Feb 28, 2013 11:52 pm
Location: Göttingen, DE

Re: Bad news about Firefox and HTML5 standalones

Post by [-hh] » Fri Feb 05, 2016 12:22 pm

We were close to an intermediate subversion of Firefox that would have brought back the "speed-browser" for use with LC's standalones (on my site Firefox is also the main browser used).
mozilla-dev 1 wrote: Should be low risk to bring back the old behavior (well, old behavior without the bug in it where exception wasn't handled properly) ... So I consider this as a low risk enough even for mozilla-release, if we do a . release
mozilla-dev 2 wrote: Unless the issue is severe enough (only one site is impacted so far) and the fix has been validated, I would hesitate to take this as a ride-along in 44.0.1 release. Sorry!
[They mean my site (because I reported to Bugzilla) and they see a few other sites linked there.]
So, LC community members, where are your sites we could report as broken with Firefox 44.0?

Of course, nobody will mind to recompile all his/her 'published' HTML5 standalone examples if a new version of LC (say dp15) runs also in the 'new' Firefox browser, if, that will be the problem, the speed of the standalones is the same.
shiftLock happens

peter-b
Posts: 182
Joined: Thu Nov 20, 2014 2:14 pm
Location: LiveCode Ltd.

Re: Bad news about Firefox and HTML5 standalones

Post by peter-b » Fri Feb 05, 2016 12:23 pm

Note that the fix for this problem in the LiveCode HTML5 engine will be released in dp-15.
LiveCode Open Source Team — @PeterTBBrett — peter.brett@livecode.com

[-hh]
VIP Livecode Opensource Backer
VIP Livecode Opensource Backer
Posts: 2262
Joined: Thu Feb 28, 2013 11:52 pm
Location: Göttingen, DE

Re: Good [was 'bad'] news about Firefox and HTML5 standalone

Post by [-hh] » Mon Feb 22, 2016 11:55 pm

Firefox versions 44 run again with LC's standalones, that are built with 8.0.0-dp15.

Perfectly done, thank you very much Peter!

This is important, because Firefox does some animations faster than all other browsers.
[Mozilla also fixed the issue (related to another) for future versions 45-47, so it's double sure.]
shiftLock happens

Post Reply

Return to “HTML5”