4 ms·

I am sorry you have to go through this painful exercise. But, how would an alternative rendering engine fix this problem?

ben-schaaf 5y ago
"Our product doesn't work in safari, use chrome or firefox instead"
- Humphrey 5y ago
  Unfortunately, Apple have a policy that the inbuilt webkit is the only browser engine that is allowed to be used on an iOS device. The iOS Chrome, Firefox, & Edge apps are just thin wrappers around the same Safari engine included in iOS.
  - paavohtl 5y ago
    We all know. @ben-schaaf was answering the question "how would an alternative rendering engine fix this problem".
- enos_feedler 5y ago
  The web is built on the foundation I can use any browser. You are going to break the fundamental promise just to avoid working around a bug?
  - rtpg 5y ago
    Sometimes browsers ship bugs of the "this API just does not work anymore" variety. When people want to get their work done, opening another browser while the original one is being fixed (which might take a couple weeks), for certain applications, is extremely reasonable for business people just trying to get their work done.
    - enos_feedler 5y ago
      that sounds like a good short term fix. I guess I was thinking about bigger things like stadia.google.com only working on Chrome browsers. It all seems arbitrary
  - ben-schaaf 5y ago
    > The web is built on the foundation I can use any browser. This foundation is provided by browsers and is also broken by browsers. If safari's foundation is broken then safari is the one not fulfilling that fundamental promise, not the websites now broken. So yes, don't use a browser if it doesn't work.
    - enos_feedler 5y ago
      I think this is a pretty harsh judgement for a webGL bug.
  - inopinatus 5y ago
    Apple have already intentionally broken that promise by refusing to implement parts of the HTML standard.
    - dmitriid 5y ago
      Which parts of HTML standard did they refuse to implement?
  - Devasta 5y ago
    "Best viewed in IE" was the norm for years and years, supporting only the major browsers has pretty much always been the case. Before Opera gave up and became another Chrome reskin, there were plenty of sites that didn't work for me until I set the user agent to match another browser.
heavyset_go 5y ago
Those WebGL bugs might not be present in other browser engines like Gecko or Blink.
sfshaw 5y ago
Webkit would have to compete with other engines to retain its market share rather than abuse its monopoly power.
- pjmlp 5y ago
  Their monopoly power is the only obstacle to the Web developers updating their CVs as ChromeOS developer.
arilotter 5y ago
Our app uses an embedded WebView. An alternative rendering engine would mean we could pin a specific rendering engine version in our app, and only update it for everyone after we work out any kinks with a new version. The current policies mean that we have zero control over Apple shipping new bugs in under our users' feet.

ben-schaaf 5y ago

"Our product doesn't work in safari, use chrome or firefox instead"

Humphrey 5y ago
Unfortunately, Apple have a policy that the inbuilt webkit is the only browser engine that is allowed to be used on an iOS device. The iOS Chrome, Firefox, & Edge apps are just thin wrappers around the same Safari engine included in iOS.
- paavohtl 5y ago
  We all know. @ben-schaaf was answering the question "how would an alternative rendering engine fix this problem".
enos_feedler 5y ago
The web is built on the foundation I can use any browser. You are going to break the fundamental promise just to avoid working around a bug?
- rtpg 5y ago
  Sometimes browsers ship bugs of the "this API just does not work anymore" variety. When people want to get their work done, opening another browser while the original one is being fixed (which might take a couple weeks), for certain applications, is extremely reasonable for business people just trying to get their work done.
  - enos_feedler 5y ago
    that sounds like a good short term fix. I guess I was thinking about bigger things like stadia.google.com only working on Chrome browsers. It all seems arbitrary
- ben-schaaf 5y ago
  > The web is built on the foundation I can use any browser. This foundation is provided by browsers and is also broken by browsers. If safari's foundation is broken then safari is the one not fulfilling that fundamental promise, not the websites now broken. So yes, don't use a browser if it doesn't work.
  - enos_feedler 5y ago
    I think this is a pretty harsh judgement for a webGL bug.
- inopinatus 5y ago
  Apple have already intentionally broken that promise by refusing to implement parts of the HTML standard.
  - dmitriid 5y ago
    Which parts of HTML standard did they refuse to implement?
- Devasta 5y ago
  "Best viewed in IE" was the norm for years and years, supporting only the major browsers has pretty much always been the case. Before Opera gave up and became another Chrome reskin, there were plenty of sites that didn't work for me until I set the user agent to match another browser.

heavyset_go 5y ago

Those WebGL bugs might not be present in other browser engines like Gecko or Blink.

sfshaw 5y ago

Webkit would have to compete with other engines to retain its market share rather than abuse its monopoly power.

pjmlp 5y ago
Their monopoly power is the only obstacle to the Web developers updating their CVs as ChromeOS developer.

arilotter 5y ago

Our app uses an embedded WebView. An alternative rendering engine would mean we could pin a specific rendering engine version in our app, and only update it for everyone after we work out any kinks with a new version. The current policies mean that we have zero control over Apple shipping new bugs in under our users' feet.