4 ms·

Developing on mobile Safari/ui+wkwebview feels very much like developing on the IE of olde. It's hard not to perceive malice in the form of wanton disregard tow

Developing on mobile Safari/ui+wkwebview feels very much like developing on the IE of olde. It's hard not to perceive malice in the form of wanton disregard towards open web technology when observing how many stupefying bugs exist in parallel to the immense profitability of the app store.

matthewmacleod 12y ago
No, it really doesn't, and you're blowing it out of proportion. What "stupefying bugs" exist in Safari that aren't much more simply explained by Apple being something of a laggard when it comes to implementing web standards?
- o_____________o 12y ago
  pointer event madness. file selector crash. <option> crash. rem bugs. insane RAM usage. crash from RAM usage. crash from greedy CSS selectors. canplay event never fired on media. That's just from the last few weeks. Can't imagine anyone who has built a moderately sized web app would think Safari's biggest problem is just being a little slow on the uptake. In better news, wkwebview is a big improvement. Hopefully it's a sign of things to come.
  - acdha 12y ago
    Do you have bug reports for any of those? That RAM usage in particular suggests that the problems are more likely either specific to your application or an extension
    - dmethvin 12y ago
      Here are some I'm aware of: https://github.com/jquery/sizzle/issues/290 https://github.com/jquery/sizzle/issues/290 https://github.com/jashkenas/underscore/issues/2081 https://github.com/jashkenas/underscore/issues/2081 https://github.com/jquery/jquery/issues/2145 https://github.com/jquery/jquery/issues/2145 Webkit devs are aware of these and they have been fixed in Webkit core, but Apple doesn't provide any info about when the fixes may see the light of day.
- untog 12y ago
  that aren't much more simply explained by Apple being something of a laggard when it comes to implementing web standards? Which is my complaint. We only just got WebGL, still no UserMedia, Fullscreen APIs. It's disappointing to say the least.
- streptomycin 12y ago
  http://www.raymondcamden.com/2014/09/25/IndexedDB-on-iOS-8-Broken-Bad http://www.raymondcamden.com/2014/09/25/IndexedDB-on-iOS-8-B...
- csytan 12y ago
  iOS Webkit still has the 300ms click event delay even though Android released a simple fix over a year ago. To work around this, you'll have to use a library like FastClick (which is not perfect) or write some Javascript to hijack touch events. I've also run into a number of CSS animation issues which are just bizzare. For example, "position: fixed" doesn't apply when a CSS transform is also applied to an element.
  - grrowl 12y ago
    I was skeptical so I looked it up: > Chrome 32+ on Android with width=device-width in the viewport meta tag doesn't have a 300ms delay, therefore listeners aren't attached. [1]: https://github.com/ftlabs/fastclick#when-it-isnt-needed https://github.com/ftlabs/fastclick#when-it-isnt-needed Android Firefox ref: https://bugzilla.mozilla.org/show_bug.cgi?id=941995 https://bugzilla.mozilla.org/show_bug.cgi?id=941995

matthewmacleod 12y ago

No, it really doesn't, and you're blowing it out of proportion. What "stupefying bugs" exist in Safari that aren't much more simply explained by Apple being something of a laggard when it comes to implementing web standards?

o_____________o 12y ago
pointer event madness. file selector crash. <option> crash. rem bugs. insane RAM usage. crash from RAM usage. crash from greedy CSS selectors. canplay event never fired on media. That's just from the last few weeks. Can't imagine anyone who has built a moderately sized web app would think Safari's biggest problem is just being a little slow on the uptake. In better news, wkwebview is a big improvement. Hopefully it's a sign of things to come.
- acdha 12y ago
  Do you have bug reports for any of those? That RAM usage in particular suggests that the problems are more likely either specific to your application or an extension
  - dmethvin 12y ago
    Here are some I'm aware of: https://github.com/jquery/sizzle/issues/290 https://github.com/jquery/sizzle/issues/290 https://github.com/jashkenas/underscore/issues/2081 https://github.com/jashkenas/underscore/issues/2081 https://github.com/jquery/jquery/issues/2145 https://github.com/jquery/jquery/issues/2145 Webkit devs are aware of these and they have been fixed in Webkit core, but Apple doesn't provide any info about when the fixes may see the light of day.
untog 12y ago
that aren't much more simply explained by Apple being something of a laggard when it comes to implementing web standards? Which is my complaint. We only just got WebGL, still no UserMedia, Fullscreen APIs. It's disappointing to say the least.
streptomycin 12y ago
http://www.raymondcamden.com/2014/09/25/IndexedDB-on-iOS-8-Broken-Bad http://www.raymondcamden.com/2014/09/25/IndexedDB-on-iOS-8-B...
csytan 12y ago
iOS Webkit still has the 300ms click event delay even though Android released a simple fix over a year ago. To work around this, you'll have to use a library like FastClick (which is not perfect) or write some Javascript to hijack touch events. I've also run into a number of CSS animation issues which are just bizzare. For example, "position: fixed" doesn't apply when a CSS transform is also applied to an element.
- grrowl 12y ago
  I was skeptical so I looked it up: > Chrome 32+ on Android with width=device-width in the viewport meta tag doesn't have a 300ms delay, therefore listeners aren't attached. [1]: https://github.com/ftlabs/fastclick#when-it-isnt-needed https://github.com/ftlabs/fastclick#when-it-isnt-needed Android Firefox ref: https://bugzilla.mozilla.org/show_bug.cgi?id=941995 https://bugzilla.mozilla.org/show_bug.cgi?id=941995