253
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 26 Jan 2024
253 points (97.0% liked)
Europe
8332 readers
1 users here now
News/Interesting Stories/Beautiful Pictures from Europe ๐ช๐บ
(Current banner: Thunder mountain, Germany, ๐ฉ๐ช ) Feel free to post submissions for banner pictures
Rules
(This list is obviously incomplete, but it will get expanded when necessary)
- Be nice to each other (e.g. No direct insults against each other);
- No racism, antisemitism, dehumanisation of minorities or glorification of National Socialism allowed;
- No posts linking to mis-information funded by foreign states or billionaires.
Also check out !yurop@lemm.ee
founded 1 year ago
MODERATORS
So that's why it interprets certain standards differently than all other engines. Must be the security. The amount of rendering errors I have to debug just for iOS is annoying. Especially, since you need a MacBook AND an iPhone to debug this bad engine properly, so either me or my employer needs to buy into their ecosystem.
Do you? WebKit is open-source and other browsers use it too, GNOME Web (Epiphany) for example.
For some reason I thought the Safari engine was proprietary, but you're right, you totally can.
However, you need to have the specific Webkit version on your system that's also used on the iOS release where the bug is present. Which can be a real pain to manage and I imagine compiling this engine will take quite a while.
Still better than buying unnecessary, overpriced hardware, though! I will for sure check this out soon.