My dislikes are a lot stronger than my likes. The checkbox for turning on and off properties is more intuitive than the Firebug cancel icon model.It can do 90% of the things I need Firebug to do, which is easily target page elements and see the CSS affecting that particular element, and then live edit those properties.The resources tab is incredibly useful.One thing is for sure, Web Inspector is pretty: You don’t get a little button you can click to pop it open, you’ll either have to right-click on an element and choose “Inspect Element” from the contextual menu, or press Command-Option-I to open it. It absolutely works, in some ways even better, but it just doesn’t feel right. The experience of using Web Inspector is a microcosm of my experience in using Safari itself. In the latest Safari, all you need to do is turn on the Developer menu in the preferences and you have access to the Web Inspector, which is Safari’s answer to Firebug. Everybody is trying to get on board now, including the Safari. Other than a code editor and the browser itself Firebug is the top web development tool of all time. Firefox stops short of the line break, which I prefer. For example, triple clicking in Safari highlights the whole line, including the line break at the end. So I definitely notice little differences in how the browsers handle text selection. So I do a lot of highlighting-and-button-clicking. I write a title, I select the text, I click a button to apply a tag around it. More than just write in it, I mark up my writing within it. So how this behaves is of grave importance to me. I write a lot in the WordPress text editor (hey, I’m doing it right now!). So let’s get on with exploring the differences. More and more sites are using progressive enhancement transitions, and I want to be seeing all that stuff.Īs I’ll go through later, there are so many tools available for both browsers than switching should (theoretically) be no big deal. In particular, Safari supports transitions and 3D transforms that are particularly cool. It’s much more of an issue on my MacBook, which sports a measly 1GB of RAM and needs all the help it can get.įirefox has pretty good CSS3 support but it lags behind Safari. In searching around, I was not alone in this. I had (before my new MacPro) an issue with Firefox where I could print a page once, but if I tried to bring up the print dialog again it was insta-crash. I’ve also had problems with some crashing in Firefox. Not that Firefox is slow, but when you spend all day every day on the web, milliseconds really make a big difference in feel. It feels like it launches faster, and it feels like it renders websites faster. I can’t even have more than one pair of shoes without getting confused. Some people claim to be able to use different web browsers for different things. No going back and forth, no half-assing it. So for an entire week, I decided I was going to suck it up and just try and make the switch to using Safari as my main web browser. I also like Apple, and when I can, I try to use Apple products. I like the peeps at Mozilla, and they do great things.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |