Supported browsers and versions for Blockly web?

[Tim Dawborn]

Hi,

Is there an official list of supported browsers and browser versions for the web version of Blockly? I can't seem to find one.

I just tried loading Blockly on very old Safari (6.2) and it's quite unhappy:

The flyout is partially hidden by the toolbox, and the scrollbars are at the top and left of the screen instead of bottom and right, and don't panning doesn't work.

Cheers,

Tim

[Rachel Fenichel]

Hi Tim,

We currently support 

• Chrome
• Firefox
• Edge
• IE
• Safari
• iOS Safari
• iOS Chrome
• Android Browser
• Chrome for Android

Touchscreen input on IE and Edge is currently spotty or broken because they implement a different API from the rest of the web (Pointer Events instead of Touch Events).

We will never support IE8 or earlier, which do not support SVG.

Our support for sounds varies by browser and platform.  On iOS we cannot load and play multiple sounds.  We do not use the web audio API because of Internet Explorer.

Cheers,

Rachel

[Tim Dawborn]

Okay, cool, thanks for that.

In that case, given Blockly master is broken on Safari 6.2, should I file a bug report, or is this outside of the lowest supported browser version?

--
You received this message because you are subscribed to the Google Groups "Blockly" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blockly+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Rachel Fenichel]

No, we aren't supporting back to 6.2 (and neither is Apple).  Of course, if you find that it's a simple thing to debug and want to submit a patch, we'll take a look.

Rachel

To unsubscribe from this group and stop receiving emails from it, send an email to blockly+u...@googlegroups.com.

[Neil Fraser]

On 25 January 2017 at 10:11, 'Rachel Fenichel' via Blockly <blo...@googlegroups.com> wrote:

We will never support IE8 or earlier, which do not support SVG.

And for completeness, Blockly is 90% working in IE9 and we could bring that to 100% with some work.  But a survey of developers last year couldn't find a single person who wanted this.  That, coupled with IE9's ever declining market share means we decided not to support it.

IE10+ is fully supported.

--

Neil Fraser
https://neil.fraser.name

[Tim Dawborn]

On 26 January 2017 at 11:43, 'Rachel Fenichel' via Blockly <blo...@googlegroups.com> wrote:

No, we aren't supporting back to 6.2 (and neither is Apple).  Of course, if you find that it's a simple thing to debug and want to submit a patch, we'll take a look.

Yup, no worries. Thanks for the clarification, I wouldn't be interested in Safari 6.2 either if it wasn't for own contractual obligations... I'll take a look at it sometime over the next week to see what the damage is.

Cheers,

Tim

[Tim Dawborn]

On 26 January 2017 at 15:06, Neil Fraser <ro...@neil.fraser.name> wrote:

And for completeness, Blockly is 90% working in IE9 and we could bring that to 100% with some work.  But a survey of developers last year couldn't find a single person who wanted this.  That, coupled with IE9's ever declining market share means we decided not to support it.

IE10+ is fully supported.

Oh, interesting. I assumed IE10 wasn't supported as there's a bunch of bugs to do with block click and dragging (i.e. block dragging doesn't work once scroll bars come into play). I'll generate some screen capture videos and file some bug reports tomorrow.

[Rachel Fenichel]

Yes, please file those bug reports.  We should work on IE 10, but our test machines are all windows 10 so our windows tests are in IE11 and Edge.

--

[Neil Fraser]

Rachel, I have a Windows 7 PC under my desk that's not going to be used for the foreseeable future.  Want it?  Comes with a KVM switch.

Send (awkwardly) from an Android phone.

To unsubscribe from this group and stop receiving emails from it, send an email to blockly+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

You received this message because you are subscribed to the Google Groups "Blockly" group.

To unsubscribe from this group and stop receiving emails from it, send an email to blockly+unsubscribe@googlegroups.com.

[Tim Dawborn]

On 27 January 2017 at 05:15, 'Rachel Fenichel' via Blockly <blo...@googlegroups.com> wrote:

Yes, please file those bug reports.

Done: https://github.com/google/blockly/issues/871

 

We should work on IE 10, but our test machines are all windows 10 so our windows tests are in IE11 and Edge.

I realise Google policy probably doesn't allow it, but FWIW, we use the free browser testing VMs provided by Microsoft to get IE and Edge machines to test on: https://modern.ie/

[Tim Dawborn]

Ah, apparently what I should have suggested was http://go/zerg :)

[Tim Dawborn]

On 26 January 2017 at 22:25, Tim Dawborn <tim.d...@gmail.com> wrote:

On 26 January 2017 at 11:43, 'Rachel Fenichel' via Blockly <blo...@googlegroups.com> wrote:

No, we aren't supporting back to 6.2 (and neither is Apple).  Of course, if you find that it's a simple thing to debug and want to submit a patch, we'll take a look.

I'll take a look at it sometime over the next week to see what the damage is.

The rendering issue was relatively easy to fix — it was caused by a missing vendor-prefixed CSS property to support older browsers. See associated PR.

Now that that particular bug is dealt with though, another bug exists whereby blocks cannot be dragged at all. I'll do some more investigation.

[picklesrus]

Thanks for the fixes!

For block dragging this is a bit of a stab in the dark, but, do you know if the regex's in https://github.com/google/blockly/blob/f5f6d69d5ef86d92e249054004c39690b0961f61/core/utils.js#L126 are matching correctly?  I think they should be even with the -webkit prefix since the non vendor specific one is set too, but that would be one of the first things I double checked.

[Tim Dawborn]

On 28 January 2017 at 04:44, 'picklesrus' via Blockly <blo...@googlegroups.com> wrote:

Thanks for the fixes!

For block dragging this is a bit of a stab in the dark, but, do you know if the regex's in https://github.com/google/blockly/blob/f5f6d69d5ef86d92e249054004c39690b0961f61/core/utils.js#L126 are matching correctly?  I think they should be even with the -webkit prefix since the non vendor specific one is set too, but that would be one of the first things I double checked.

No worries. I thought it was going to be the regex's too, but that turned out to be a wild goose chase. The non-movement was caused by a typo I made elsewhere. Safari 6.2 seems to be good now with those two PRs accepted. I don't have any other Safari machines between then and Safari 10 to test on though.