ForgottenFlux@lemmy.world to Technology@lemmy.worldEnglish · 8 months agoApple is finally allowing Firefox to use its own engine on the iPhone (but only in the EU)www.theverge.comexternal-linkmessage-square21fedilinkarrow-up10arrow-down10
arrow-up10arrow-down1external-linkApple is finally allowing Firefox to use its own engine on the iPhone (but only in the EU)www.theverge.comForgottenFlux@lemmy.world to Technology@lemmy.worldEnglish · 8 months agomessage-square21fedilink
minus-squarewillya@lemmyf.uklinkfedilinkEnglisharrow-up0·8 months agoThanks. Do you have an example of the super weird rendering? Also are none of what you’re saying here togglable in the WebKit Feature Flags to mess around with bleeding edge features?
minus-squareTrickDacy@lemmy.worldlinkfedilinkEnglisharrow-up0arrow-down1·8 months agoEvery time I want to use a new feature of web browsers, if support stops me from doing so, it’s always safari to blame.
minus-squarewillya@lemmyf.uklinkfedilinkEnglisharrow-up0·8 months agoWhat was that last or current feature you’re missing out on and what’s the use case?
minus-squareTrickDacy@lemmy.worldlinkfedilinkEnglisharrow-up0arrow-down1·8 months agoI really can’t remember an example off the top of my head. Over the last 5 years it’s probably been an issue more than 20 times.
Thanks. Do you have an example of the super weird rendering? Also are none of what you’re saying here togglable in the WebKit Feature Flags to mess around with bleeding edge features?
Every time I want to use a new feature of web browsers, if support stops me from doing so, it’s always safari to blame.
What was that last or current feature you’re missing out on and what’s the use case?
I really can’t remember an example off the top of my head. Over the last 5 years it’s probably been an issue more than 20 times.