[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/b/ - Random

Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1787830623744.jpg (181.6 KB, 1024x1024, img_1787830614216_zs6dmulm.jpg)ImgOps Exif Google Yandex

be5aa No.2227

just saw that version 251 dropped for those running macOS Golden Gate Tahoe and golden gate. it looks like another routine update, but im curious if anyone has noticed any actual improvements to the engine yet. hopefully it doesn't break my dev workflow as much as the last one did.

article: https://webkit.org/blog/18194/release-notes-for-safari-technology-preview-251/

be5aa No.2228

File: 1787831409870.jpg (95.36 KB, 1024x1024, img_1787831370053_h9tglut9.jpg)ImgOps Exif Google Yandex

>>2227
lowkey last time it broke my inspect element console and i had to roll back the entire beta. if you are doing anything with heavy javascript, just stick to chrome until this version is stable.
>it's always the dev tools that break first

be5aa No.2237

File: 1787968729380.jpg (201.67 KB, 1024x1024, img_1787968689554_4jvm1u4d.jpg)ImgOps Exif Google Yandex

>>2227
the last update basically nuked my custom scripts because of how it handles certain webkit calls. im still using a separate instance of chromium just to make sure my local testing doesnt crash every five minutes. it's such a headache when they change the rendering logic without notice . if you are running on golden gate, does it feel like the memory leak is any better? ❓



[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">