[cryodesign]

I'm a designer, so definitely interested in this. But I got a 'Sorry, our editor is optimised for Chrome' message.

I'm using the latest version of Firefox... what features does Chrome have that FF hasn't?

I get it's early stage, so you might have just done a blanket 'If not Chrome show message' check.

If the latest version of FF can support, I would do a more fine grained check.

Will check with Chrome later...

[aczerepinski]

From the site: "Pagedraw generates code guaranteed to work correctly and in all browsers".

So luckily they can fix this issue by re-generating their site, using their site.

[jpochtar]

Actually, yes! All the parts of our site which are made in Pagedraw are fully cross-browser supported. That includes our landing page, dashboard, and parts of our editor.

Based on the feedback in this thread we're going to bump up the priority of this concern. Getting this kind of feedback is why we're doing this launch thread, so we really appreciate it.

[ta1519687540]

I will sound harsh but I'm really curious so I have to ask:

- What was the thinking behind supporting only Chrome?

- For a tool that support cross-browser, wouldn't it expected that tool itself runs on multiple browsers?

- Is it really reasonable not to spend time to support multiple browsers and have let possible first adapters to have bad taste with the product ?

[raphaelrk]

I just tried spoofing my user-agent with Firefox, editor and preview worked but the designer was pretty broken. It seems Firefox and Chrome still have slightly different ideas about how layout is supposed to work, would be curious to hear what the differences are.

Super excited for the Figma + React-native support, I think ~20% of my time this past month was converting our designer's figma sketches into react native!

[jpochtar]

We had a good conversation about this before down at https://news.ycombinator.com/item?id=16468276.

tl;dr: would you like the Electron app instead? It's available at https://documentation.pagedraw.io/electron/

It was tough for us, because we're big believers in the standards-based web. We 100% promise that all the code we generate works across all browsers.

Our editor was almost electron-only, but felt it was better to launch with Chrome + Electron than just Electron. Our editor isn't a normal webpage; it's doing all kinds of crazy nonstandard things webpages shouldn't do. It's only in the browser at all so we can re-use a web engine as our editor's rendering engine, since we occasionally show you snippets of compiled code.

I'm personally really sorry as an engineer that we don't support Firefox, Safari, and other browsers yet. It's on our roadmap :)

[WhitneyLand]

Do you mind sharing some of the primary reasons this is required by your editor?

>all kinds of crazy nonstandard things webpages shouldn't do

[jpochtar]

- until recently, there wasn't a universal cross-browser API for pinch zoom support. Not sure if that's still the case.

- we do a lot of work with the selection/focus browser API, which doesn't always work the same / have the same APIs

- until recently, Firefox had a different opinion about where an outline should go wrt positon:absolute children

...and what seems like a million more little things. We decided it was more practical to do Chrome + Electron (basically the same) than try to cover every browser where the standards don't exist or aren't met, since we're touching a lot of surface area and weird corners of the browser.

[WhitneyLand]

Thanks. I think it’s a good decision, it seems like a classic example of needing to recognize sometimes going against conventional wisdom makes the most sense given particular circumstances, like gaining critical mass in a start up. As to where the right decision might be different for a later stage company.

[cryodesign]

Hey thanks for explaining and like I said - I get it's early stage - was just curious what was missing in FF.

Anyway, will try out the Electron version and definitely be keeping an eye on this one...