341–350 of 465 posts
I switched to Firefox, and I was blown away to find that Google Meet (the new Hangouts) does not work. You just get the message "Meet doesn't work on your browser". I'm also impressed at how many of my job's internal websites don't work. This doesn't bug me as much, but it's obvious the devs who created them didn't even do a sanity check in Firefox.
Earlier quoted context omitted.
"For some reason" I think we should probably expect the Cable News Network to traffic heavily in video, yes?
If you've ever watched History or The Learning Channel, you might not expect much anymore.
developers grouse about the other browser makers who are “holding the web back.” Indeed, perhaps "holding the web back" is a good thing if it means websites will be more accessible overall, to even less common browsers like NetSurf, Dillo, and all the other text-based ones. IMHO the "feature war/race" between the major browser vendors has had an overall negative effect, as if all sites somehow need to turn into ridic…
i really wish the standards bodies would make a concerted push for a solid advance in CSS (flexbox and css grids are pushing that way but are relatively complex), so that we could get rid of DIV-itis. it's like the TABLE-itis of the past, but two letters shorter (i'm exaggerating, but still...). that would not only clean up the html but make both learning and development faster. they should also really advance basic…
We're trying. Grid (also Flexbox, but mainly grid) should be a large part of the solution, as it significantly reduces the need for divs that are just there for layout purposes. display:content should also help disconnecting your markup needs from your styling needs somewhat (go shout at browsers if it's not coming fast enough). We've also recently decided to add multiple borders, so that you don't need to add a bunch of nested divs just to have nested borders.
The last piece of the puzzle would probably be to be able create boxes (or trees of boxes) without markup, and inject content from the DOM into these boxes. That would be fantastically useful, and has been explored before, but it turns out it is a really hard problem. The first attempt at this is css-regions, which ended up being rejected, in part by Google (because they thought the complexity needed for the implementation was excessive), in part by Mozilla (because they thought the design didn't fit well with how everything else works and would break in too many cases. Also, complexity).
A more modest attempt has been outlined here https://drafts.csswg.org/css-overflow-4/#fragmentation but it is still only an early draft, and solving that isn't trivial either.
"Safari ships new features on a much slower cadence, but they’re usually solid and always perform incredibly well" Well, clearly this person doesn't have much experience with web development... The webengine in iOS is the biggest pile of crap I've ever worked with since IE6. "Oh? You want to click this? OK, let's wait for 300 ms just in case you want to double tap to scroll!" "We finally fixed it, no more delay on cl…
What really sucks is that Apple has TENS OF BILLIONS of dollars in cash, and yet can't be bothered to throw a billion at fixing iOS, iOS safari and MacOS bugs. Its quality really went downhill. I really loved the "it just works" stuff of Apple Past. And I loved the intuitive, skeumorphic interfaces. Now it's all crap and HIDDEN MODES - something Apple always spoke against in its UX manuals. It's sad day that Google a…
And the worst: Endless "back" button/swiping on the News app.
Earlier quoted context omitted.
Yah, I keep tabs on that stuff. But most of my clients actually use Apple hardware for a few years now, and even if this update goes out tomorrow, and all iOS 11 users get it. iOS 10 users and below are out in the cold, and that accounts for 99% of my users. And you know what it's like trying to use a feature even when 70% of users can take advantage of it, it's still a no-go. So Apple totally blew it on this one. MS…
Apple has unusually high adoption (compared to Android) for new versions of their OS, I am not too worried. You can ship a service worker and it will not degrade the experience for users on older browsers.
Earlier quoted context omitted.
Maybe we can split the difference. Chrome == IE because of breaking standards, and Safari == IE because it is so far behind on supporting standards. Also, both Chrome OS and iOS, both have integrated their browser into their OS and don't allow competition from other browsers on their platforms. Is that a fair assessment?
Yeah I think it's a totally fair assessment. And it's right to be wary of Apple. They have many of the same negative incentives as Microsoft had: if the web outshines their proprietary app platforms, then what good are those platforms? However, out of the two behaviors ("embrace and extend" versus "slow standards adoption") I think that Chrome's "embrace and extend" is the one that's actually a threat - and to me, th…
But if your client only runs iOS for their entire business, you can't even complain about Chrome to them. And if their browser doesn't support something as simple as offline html5 features properly, and you need this, across multiple platforms (cause they have a few laptops too). Then you can't use a browser based platform. Or if you do, you have to live with many compromises.
This is how I see Apple working. If the market didn't force them to upgrade Safari, I think they never would. They'd just say "browsers are for html, and the Apple App Store is for everything else".
But my client just wanted their stupid form to work offline. At least Chrome can do this, their adding of extra stuff doesn't _limit_ what is possible.
And I don't think many of these features are "new and shiny", I think they are fundamental to the web now. If they were new and shiny only, then Firefox would have had it's ass handed to it by the big-boys. But instead, we see MS and Apple falling behind a simple non-profit in the web standards support area.
Remember, Apple has more money in the bank than any company ever in the history of the world. It's a choice they are making not keeping up with web standards.
So the question has to be asked, what benefit does Apple get from keeping web standards very low on it's locked down platform? (any answer besides forcing devs into their store?)
Earlier quoted context omitted.
i really wish the standards bodies would make a concerted push for a solid advance in CSS (flexbox and css grids are pushing that way but are relatively complex), so that we could get rid of DIV-itis. it's like the TABLE-itis of the past, but two letters shorter (i'm exaggerating, but still...). that would not only clean up the html but make both learning and development faster. they should also really advance basic…
CSS Working group person here. We're trying. Grid (also Flexbox, but mainly grid) should be a large part of the solution, as it significantly reduces the need for divs that are just there for layout purposes. display:content should also help disconnecting your markup needs from your styling needs somewhat (go shout at browsers if it's not coming fast enough). We've also recently decided to add multiple borders, so th…
But in the case of Microsoft, they made 2 horrible mistakes:
- Piss off the user (slow, frustrating performance, popups, leaving people vulnerable to malware)
- Piss off the developer (incompatible behavior)
I think Microsoft saw web applications as a competitor for desktop development (e.g: Visual Studio), and they felt the urge to cripple it.
Your average user had IE with 100 toolbars installed and horrible performance, you could not do anything.
As a result, IE and all successors are dead to me. Never going to use it again.
https://i.stack.imgur.com/82hWm.jpg
^ That's why we hate you Microsoft.
Each time I delete the Edge icon, I restore it only to delete it again, and again, and again, each time bringing more satisfaction.
That satisfaction is only surpassed by the one I get when I delete a Windows partition.
Earlier quoted context omitted.
Oh so you want a large canvas on an iPad? No, F you. That might impact performance so we restrict it.
Some of the iPads have a very limited amount of memory e.g. 1GB. I think users would be expecting Apple to curtail your ability to crash or hang the browser.
What I really hate is that when safari shits itself the message to the user is “there was a problem with the web page so it was reloaded” so we get old iphone users complaining to us when their lame browser crashed.
That and iframes getting resized to full height ignoring css directives completely... we have a lot of our codebase that are workaround just for ios
