Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Safari Ruined My Tuesday

fly.io

Post reply on HN
Print view View original

101–110 of 140 posts

Re: Safari Ruined My Tuesday

#101

Post by chrismccord »

Ciantic wrote: post #81

> CSS includes a handy pointer-events attribute that makes buttons and links flip to non-interactive Except that it doesn't, you can still focus those with keyboard and click them. You should always disable buttons with `disabled` property instead of that hack.

In this case, the rule is for all interactive elements. It's not just buttons, but anchor tags as well (or any other element a user decides to put a `phx-click` and friends on. Phoenix LiveView internally already noops if it's not connected, but we used the css rule so the cursor pointer would not reflect an interactive element while in a loading state.

Re: Safari Ruined My Tuesday

#102

Post by PostThisTooFast »

stjohnswarts wrote: post #57
Benjamin_Dobell wrote: post #15

Earlier quoted context omitted.

It's really not just "trendy". Safari is the bane of my existence. On Big Sur, our WebGL app was occassionally sporadically rendering floating objects and black primitives into infinity on our CEOs laptop. On the plus side, our competitor's product didn't work at all. So I guess it's not all bad. In this case, Catalina had worked fine, and upgrading to Monterey fixed the issue. So props to Apple for fixing the proble…

I guarantee it's not the latter given Apple's almost infinite resources.

Wrong. Apple often just gives up on design work and shits out another obscure, overly complicated, and defective “solution” to simple problems.

Try copying some styled text from somewhere and pasting it at the end of a Mail message. Then try to get out of the pasted style and continue typing in “normal” style.

Pathetic.

Re: Safari Ruined My Tuesday

#103

Post by chrisseaton »

Vinnl wrote: post #75

Heh, reading the title I thought this was going to be someone losing all their tabs because "clear history" on mobile Safari apparently does that: https://twitter.com/SaraSoueidan/status/1457307545815732233 > Oh dear God.. Clearing history on Safari iOS closes all currently-opened tabs?! Why is there nothing that warns you of that?! Why does clearing history on mobile work differently from the way it does on mac? I h…

> I had 60+ important tabs open and now they're gone!!

This just doesn't seem a reasonable expectation that these are preserved - they would also be lost if the computer crashed wouldn't they?

If it's important then save it.

Re: Safari Ruined My Tuesday

#104

Post by merrywhether »

Benjamin_Dobell wrote: post #15
syspec wrote: post #8

I encounter random CSS bugs all the time in Chrome, it's just trendy to say Safari is behind the times. Google wants everything to be done in the browser, their browser, so they can track everything without cookies to sell ads

It's really not just "trendy". Safari is the bane of my existence. On Big Sur, our WebGL app was occassionally sporadically rendering floating objects and black primitives into infinity on our CEOs laptop. On the plus side, our competitor's product didn't work at all. So I guess it's not all bad. In this case, Catalina had worked fine, and upgrading to Monterey fixed the issue. So props to Apple for fixing the proble…

I actually like that they do this and let me use the UI I know and that will definitely work. 99% your video playback UX is not as good and you mostly want to take over full-screen so you can prevent the user from doing things (you may fall in the 1%, but I’m generalizing so apologies if you’re one of the few exceptions). It’s annoying on the iPad when sites build half-cocked full-screen UIs with buggy custom controls.

Re: Safari Ruined My Tuesday

#105

Post by [deleted] »

frou_dh wrote: post #94
klodolph wrote: post #5

> It's like living with IE6 again There is a CSS bug. CSS bugs are dirt common. It's a miracle that there are as few CSS bugs as there are. However, I remember IE6. IE6 was a total fucking mess. Everything was broken on IE6. It wasn't just a bug, it was a complete support nightmare. I routinely encounter problems with CSS that reveal maddening differences between Chrome, Firefox, and Safari. That's just for desktop.…

Most Safari comment threads have people looking for an excuse to use the phrase "The new IE" as if it's a zinger they came up with.

[deleted]

Re: Safari Ruined My Tuesday

#106

Post by Matthias1 »

When you're doing cross-platform development like this for the web, you're going to have a "least common denominator" that you have to design for. Safari is that least common denominator right now only because Microsoft switched to using Chromium. But if Apple switched Safari to use Chromium, then Firefox would be the least common denominator and supporting Firefox would suddenly seem like a burden.

It's fine to criticize Safari and encourage Apple to do better in the space, since Apple isn't super incentivized to improve Safari. But this narrative that always targets the browser with the smallest feature-set at any given time will only stop when all browsers are Chromium based. (At which point they'll start complaining about other browsers using a Chromium version that's slightly behind Chrome.)

Re: Safari Ruined My Tuesday

#107

Post by Benjamin_Dobell »

merrywhether wrote: post #104
Benjamin_Dobell wrote: post #15

Earlier quoted context omitted.

It's really not just "trendy". Safari is the bane of my existence. On Big Sur, our WebGL app was occassionally sporadically rendering floating objects and black primitives into infinity on our CEOs laptop. On the plus side, our competitor's product didn't work at all. So I guess it's not all bad. In this case, Catalina had worked fine, and upgrading to Monterey fixed the issue. So props to Apple for fixing the proble…

I actually like that they do this and let me use the UI I know and that will definitely work. 99% your video playback UX is not as good and you mostly want to take over full-screen so you can prevent the user from doing things (you may fall in the 1%, but I’m generalizing so apologies if you’re one of the few exceptions). It’s annoying on the iPad when sites build half-cocked full-screen UIs with buggy custom control…

As mentioned, our app is WebGL i.e. interactive real-time rendering, not at all video playback.

That said, I agree with you on custom video UIs being horrid.

Re: Safari Ruined My Tuesday

#108

Post by merrywhether »

innocenat wrote: post #60
fouc wrote: post #55

Earlier quoted context omitted.

Code to webkit's standards. Also you're forgetting iOS is largely Safari (or chrome/firefox wrapped in webkit).

Tbh, personally, I only care about Safari because iOS. If iOS user are able to use other browsers, I wouldn't really hesitate to not support Safari.

Are you saying you basically want a Chrome monoculture? It would be terrible to give that much power to Google.

Re: Safari Ruined My Tuesday

#109

Post by merrywhether »

Mikeb85 wrote: post #12
blondin wrote: post #11

i sympathize with the author. safari and browsers aside, there is something bigger going on. there is a massive disconnect between applications users and makers nowadays. i have started to think that they a) don't care b) have misaligned priorities c) have weird notions of "acceptable" errors. i have a long list of applications that break every time there is an update. even UX updates introduce bugs nowadays. i have…

Why should any developer care about supporting Safari? Chrome and Firefox support most (all?) of the current web standards. Every site I use works on both. I don't hear any concerns about Brave, Edge or Opera either. How is it that Safari is the only broken browser these days? As for 'acceptable' errors, I find software to be pretty reliable these days. I remember way more things being messed up back in the day...

There are no web standards in the era of WHATWG. It’s just a living spec composed of whatever vendors build and convince other vendors to add to their own products. Chrome is constantly spitting out new proposals that are already half-baked-but-live in their browser and then people start using them and complain they aren’t yet in other browsers. Yet when Safari or Firefox add new features we don’t act like Chrome is slow? Chrome’s rapid pace is almost surely an effort by Google to overwhelm the competition so they can make more ad money through dark patterns via Chrome dominance.

Re: Safari Ruined My Tuesday

#110

Post by kalleboo »

Eric_WVGG wrote: post #84
reaperducer wrote: post #9

Earlier quoted context omitted.

You might be surprised how often a CSS bug will break an entire site. I've seen it many times in my decades.

Oh, I’ve got a good one about this. Back in 2000, I was living in a new city, and cold-calling graphic design firms. At the time, most of the web looked like utter ass, and my feeling was that it made more sense to try to be the in-house developer for designers, rather than try to bring design to web development firms. So I put together a resume with my personal URL placed prominently across the top, and knocked on t…

That's fantastic! I have the opposite story - we sold opinionated Mac software bundles, and one of the perks was we could use the latest Apple-only Safari CSS tricks (this was before Chrome forked from WebKit and Safari was actually leading the way with stuff like CSS transitions/animations and Canvas). Microsoft released free VMs for browser testing in IE and I tried it for kicks, and indeed, our page would literally crash IE when loaded (of course Windows had protected memory so the OS wouldn't crash). We wore it as a badge of honor.
Post reply on HN