![]() What I do like about Safari is that ALL ASSETS used on a page are listed and can be fully inspected, including things like Google Fonts, for example. ![]() This is what Safari Web Inspector looks like: Photo by Interglobalmedia on Interglobalmedia That is because of all those Chrome background trackers and plugins that exist in the browser, and which can severely damage site performance. lots of images that have lazy-loading implemented, the Lighthouse audit in Firefox is double the score of Chrome, and load time in general is very quick in Safari. AND when I use Safari or Firefox to land on sites which are asset heavy, i.e. Chrome has to go, except for when testing for cross-browser compatibilities. I think I will be working between Firefox and Safari. They are much better than they used to be, and they DO have a Chrome Sources tab equivalent. Which just did not seem to initially work for me. AND there is no Chrome Sources tab equivalent. ![]() That definitely is more secure and private, but the DX is not the best as far as their browser tools go. And that is NOT good and NOT secure.īelow is a screenshot of Chrome Developer Tools when I go in using the Option + Command + J short cut and select the Sources tab: Photo by Interglobalmedia on Interglobalmedia However, I have also very recently been getting “unknown” notifications from Chrome, which I absolutely know must be from “phishing” sites. Until very recently, I preferred working with Chrome Developer Tools, because I considered the DX ( developer experience) the most intuitive. And it is not necessarily for the “obvious” reasons. I just found out why some developers prefer working with Chrome Developer Tools, some prefer working with Firefox Browser Tools, and some prefer Safari Web Inspector.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |