Hacker News Reader

Comment by diggan | Hacker News Reader

> Currently the latest version of Chrome is the only browser that supports the advanced and exciting features we've built into Construct 3. We hope to add support for other browsers once they catch up with us!

What features are currently missing from Firefox to be allowed to use Construct 3? Seeing more and more errors like this lately, and most of the times the features the developers don't think Firefox supports, actually exists.

Edit: Running Firefox 52, I get a list of features that are not supported yet that is needed, so seems legit.

If you want to try Construct 3 anyways on Firefox, you can enable dom.webcomponents.enabled and dom.dialog_element.enabled while running Firefox 53 in about:config, and everything should work fine. Firefox 53 is supposed to be released 2017-04-18.

Thanks to the team behind Construct to actually use feature detection instead of user agent sniffing to block browsers.

View on HN

We are obviously extremely incentivised to support as many browsers as we can right now, but Chrome is the only one that can run it (nearly) out the box.

Firefox is close, but is missing HTML imports and Dialog element. If you open: https://editor.construct.net/

It will list the missing features.

I wasn't familiar with HTML imports, and after searching around it looks like Firefox will never support (https://hacks.mozilla.org/2014/12/mozilla-and-web-components...). Any plans for polyfills, etc.?

We can potentially polyfill them - we're waiting for dialog element support first, that's still holding back support in most other browsers. HTML imports are outrageously under-valued as a technology for building this kind of web app. We're hoping to do some blog posts highlighting how awesome they are and try to turn around opinion on that.

Can't you just... program that stuff yourself? By relying on such "cutting-edge" features, you get all the drawbacks of web technology with none of the reach.

No, HTML imports are the kind of technology that are the perfect architecture for this kind of web app and arguably are what make it possible. It'd take a whole blog post to explain, hopefully I can write it up soon!

There are web applications that are way more demanding than this, that have run on more platforms for a while and that don't need any of these questionable experimental features.

I could understand if you said you need WebGL or WebAudio or some other hardware/OS interface. You don't need HTML imports.

Perhaps I should have added another qualifier: for a team of three developers. (One initially.)

...even for a team of one developer!

Look, I understand how one might like HTML imports. Once you've gone down the rabbit hole of Web technology, all the fancy experimental features make it look like HTML/CSS are now adequate. They're not. It's a trap.

The real answer is writing Javascript (or something that compiles to Javascript). Always has been, always will be. Don't trust the web consortium to specify things that maybe browser vendors will implement. Do it yourself now, thank yourself later.

What are you trying to achieve here? Make them rewrite the whole project from scratch? You made your point clear in your first reply.

We took the same bet with CSS grid, and it paid off. Lots of features can make a massive improvement to the development experience. We used a wide range of experimental features starting around 2014. Most of them came to fruition. HTML imports has been the only tricky one so far, which I think is a pretty great result on all the bets we took.

Aside: what's dialog supposed to be for, sounds like it will be great for malware.

Reply on news.ycombinator.com