21–30 of 59 posts
Scrolling is broken in Safari on this page. Maybe the page authors should spend less time in the Chrome dev tools and more in the dev tools of other browsers.
Edit: This may help: https://www.mozilla.org/en-US/firefox/new/
Scrolling is broken in Safari on this page. Maybe the page authors should spend less time in the Chrome dev tools and more in the dev tools of other browsers.
I'm glad these folks spend their time on Chrome dev tools rather than catering to the users of inferior browsers who expect people to invest extra energy catering to their preferences. Edit: This may help: https://www.mozilla.org/en-US/firefox/new/
My main issue, FWIW, is not that Apple don't fix bugs - it's the long timeframes they take between releases!
I ask this because I've been trying to track down an issue - probably caused by an ad on a news website - where Chrone pretty much freezes up on all processes. Whilst I can (and have) worked around it by installing uBlock Origin in browsers I'd really like to know what is causing the problem. I can't produce it locally so I'd like to get a log of all things that occur on Chrome over the course of a day.
They mention "Progressive web apps" and link to some info, but I can't figure out what the difference is from a normal webpage. Do they mean "web apps that use some stuff that was recently added to most modern web browsers"?
Scrolling is broken in Safari on this page. Maybe the page authors should spend less time in the Chrome dev tools and more in the dev tools of other browsers.
Earlier quoted context omitted.
I'm glad these folks spend their time on Chrome dev tools rather than catering to the users of inferior browsers who expect people to invest extra energy catering to their preferences. Edit: This may help: https://www.mozilla.org/en-US/firefox/new/
Whilst the issue may not be the fault of the web designers, there's not really any need to call Safari inferior. It's probably a bug, all browsers have them. My main issue, FWIW, is not that Apple don't fix bugs - it's the long timeframes they take between releases!
Earlier quoted context omitted.
Whilst the issue may not be the fault of the web designers, there's not really any need to call Safari inferior. It's probably a bug, all browsers have them. My main issue, FWIW, is not that Apple don't fix bugs - it's the long timeframes they take between releases!
Rarely is any description 'needed', but in this case it is 'helpful'. The parent seems to be unaware that Safari has, over time, become inferior (relative to the other popular browsers) increasing the likelihood that the problem is with safari rather than with the site. Being unaware of the inferiority of safari, he didn't even try another browser. Simply knowing that its a safari bug may not be sufficient to maximiz…
Scrolling is broken in Safari on this page. Maybe the page authors should spend less time in the Chrome dev tools and more in the dev tools of other browsers.
I'm glad these folks spend their time on Chrome dev tools rather than catering to the users of inferior browsers who expect people to invest extra energy catering to their preferences. Edit: This may help: https://www.mozilla.org/en-US/firefox/new/
Earlier quoted context omitted.
Rarely is any description 'needed', but in this case it is 'helpful'. The parent seems to be unaware that Safari has, over time, become inferior (relative to the other popular browsers) increasing the likelihood that the problem is with safari rather than with the site. Being unaware of the inferiority of safari, he didn't even try another browser. Simply knowing that its a safari bug may not be sufficient to maximiz…
What, specifically, do you consider inferior about Safari? I'm genuinely curious - I use Chrome, Firefox and Safari regularly and I find Chrome and Safari to be of equal quality. And I notice bugs in Chrome every now and then, but with both browsers I find it pretty rare these days.
As another for-example, I was able to hard-crash safari on ios by setting some CSS attributes on the scroll track about eight months ago - like literally a web page with css that altered how wide the scroll bar track was could CTD safari on ios.
As another for-example, KeyboardEvent.key isn't supported in safari.
As another for-example, http://caniuse.com/#compare=chrome+51,safari+9.1,ios_saf+9.3 and scroll down. Battery Status API, Fetch API, Proxy Objects, Shared Web Workers, on and on. The "modern" web as a good platform for interesting progressive apps is passing safari, in particular iOS users, by.
One assumes a motivator here is the app store: apple's walled garden approach is fundamentally incompatible with web apps gaining all these APIs, whereas android's (relative) openness means Google is less uptight about people deploying apps without going through the app store approval process.
Scrolling is broken in Safari on this page. Maybe the page authors should spend less time in the Chrome dev tools and more in the dev tools of other browsers.
I really wonder what really causes it.