When there are many tabs open, dont you think it would be much faster to recognize the content of the tab, when you see the icon of the tld? Like an apple in case of macrumors?
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apple Releases Safari Technology Preview 3 With Extensive Tweaks and Bug Fixes
- Thread starter MacRumors
- Start date
- Sort by reaction score
Bingo! This removal of graphical elements (especially shapes / icons... or using nondescript ones), removing color, or even possibly things like hiding aspects of the URL are bad UX/UI moves.
It makes no sense in terms of UX and usability. And that's what a browser should aim for. It's not a peace of design furniture.
Definitely not. If I have 6 Stack Overflow tabs open, I want to see more title so I know which tab is that Javascript bit I was looking up rather than see that I have 6 tabs open from the same site. If I have multiple Google searches open, same thing: I want more title excerpt to know which tab is which search rather than a sea of the same logos.
This is actually one of the biggest UX problems in Chrome where, if sufficient tabs are open, they shrink down to icons and no text. Safari takes a different approach in limiting how small tabs get so that they're actually useful when you have a large number of them open.
Interesting, didn't have that case often to think of this in your perspective. It would be so simple for safari and chrome: let users in the options decide to use icons or not.
Sorry, just saw your question (not a regular commenter)!
Most stuff (in Webkit/TP at least) is prefixed, so Grid is currently behind the -webkit- prefix (IIRC), if you're using chrome/firefox/opera it's behind a flag e.g. 'experimental web platform features', just google 'enable css grid in 'x' browser' and there'll be step by step guides to doing so.
Hehe, thanks... but that's kind of the problem. I must be missing something fundamental, as I've never tried using experimental stuff like that yet. Every 'tutorial' I've been able to find doing searches like that just says to enable it with the -webkit- flag.
Looking at similar searches for other browsers, there seems to be a 'settings' page you can get to with such a flag to turn the experimental stuff on or off. I've not been able to find that for Safari. And, I've yet to find a tutorial that explains it.
Hehe, thanks... but that's kind of the problem. I must be missing something fundamental, as I've never tried using experimental stuff like that yet. Every 'tutorial' I've been able to find doing searches like that just says to enable it with the -webkit- flag.
Looking at similar searches for other browsers, there seems to be a 'settings' page you can get to with such a flag to turn the experimental stuff on or off. I've not been able to find that for Safari. And, I've yet to find a tutorial that explains it.
Well in Firefox Nightly (v49) and the current Safari Technology Preview (5) CSS Grid is now enabled by default/unprefixed so you don't need to mess with any of that!
But for future reference you will likely encounter other things behind flags (prefixes are being killed thankfully but many things are still prefixed) so...
For features behind flags search in the URL/ominbox: For Chrome & Opera go to/search 'chrome://flags', for Firefox go to 'about:config', not sure about Webkit/Safari but they may not have any flagged features yet anyway. Then there will be a settings page with a bunch of features in development that you can turn on if you want to try them out, these can affect the stability of the browser so be warned.
For prefixes, just prefix the property or value with the vendor prefix (-ms-, -o-, -webkit-, -moz-) and use it as you normally would (there are occasionally syntax differences which you may need to look up). For example (and kinda redundant now):
body {
display: -webkit-grid;
-webkit-grid-columns: auto;
-webkit-grid-rows: auto;
}-webkit-grid-columns: auto;
-webkit-grid-rows: auto;
There's a wealth of info for support for CSS and JS on caniuse.com, which i recommend checking out.
Well in Firefox Nightly (v49) and the current Safari Technology Preview (5) CSS Grid is now enabled by default/unprefixed so you don't need to mess with any of that!
But for future reference you will likely encounter other things behind flags (prefixes are being killed thankfully but many things are still prefixed) so...
For features behind flags search in the URL/ominbox: For Chrome & Opera go to/search 'chrome://flags', for Firefox go to 'about:config', not sure about Webkit/Safari but they may not have any flagged features yet anyway. Then there will be a settings page with a bunch of features in development that you can turn on if you want to try them out, these can affect the stability of the browser so be warned.
For prefixes, just prefix the property or value with the vendor prefix (-ms-, -o-, -webkit-, -moz-) and use it as you normally would (there are occasionally syntax differences which you may need to look up). For example (and kinda redundant now):
body {
display: -webkit-grid;}
-webkit-grid-columns: auto;
-webkit-grid-rows: auto;
There's a wealth of info for support for CSS and JS on caniuse.com, which i recommend checking out.
Thanks Josh... most of that is what I've found. But, supposedly, there is a way to enable it in Safari (but, I'll try again with the most recent, if it's on by default!). Lots of stuff references turning it on in Safari, but I couldn't find any way to do so.