21–30 of 76 posts
I only used it for a very specific reason - I had a script which removes multi-item eBay listings where one item is 99 cents (typically some kind of keychain) and the other items are the actual listed item at a much higher price.
It's a technique used to break the "sort by price" function, since it sorts by the cheapest item in a multi-item listing.
> Added support for FIDO2-compliant USB security keys with the Web Authentication standard in Safari on macOS. well this makes me happy at least
This is awesome for WYSIWYG editors, most of which have struggled to keep the formatting toolbar visible on mobile screens because there's been no good way to detect whether the keyboard is open.
Apple removed the ability to use uBlock Origin or similar. I tried few ad blocker from the app store, but non of them block Youtube's video ad, making it useless. We still have Firefox for now I guess.
Apple removed the ability to use uBlock Origin or similar. I tried few ad blocker from the app store, but non of them block Youtube's video ad, making it useless. We still have Firefox for now I guess.
* Added support for the Pointer Events API enabling consistent access to mouse, trackpad, touch, and Apple Pencil events. https://caniuse.com/#feat=pointer - now you can use one unified event capture everywhere, instead of having to choose between "click" and "touch"!
Safari is the new internet explorer. Too little, too late.
Nope. Chrome is the new IE. Standards don't matter when you have a high enough market share- you can do whatever you want and people have to support it. IE was the reference browser for the web in the 90s, and Chrome is that today.
It's not quiet that precise -- there was a transition period at the end of the 90s and a period of multipolar quasi-equanimity before Chrome's dominance -- but it's a decent first approximation.
* Added support for the Pointer Events API enabling consistent access to mouse, trackpad, touch, and Apple Pencil events. https://caniuse.com/#feat=pointer - now you can use one unified event capture everywhere, instead of having to choose between "click" and "touch"!
In my experience writing a component suite I have found I don't use touch[a-z]+ events that much (just like mouse[a-z]+ events don't get used much either).
I would be very careful before believing the promise of Pointer Events, unless you need to be on the bleeding edge for some reason. When I first used Pointer Events, there were heaps of corner cases that bit me hard. I would be especially careful if using them with virtual Dom updates or very dynamic pages - one of the worst pain points was issues with events when elements were deleted/replaced.