Re: Yahoo! expands its usage of PHP - one of our best wins yet?
| From: | Terence Kearns | Date: | Thu, 07 Nov 2002 23:41:54 +0000 |
| Subject: | Re: Yahoo! expands its usage of PHP - one of our best wins yet? | ||
| References: | 1 2 3 | Groups: | php.evangelism |
| Request: | Send a blank email to php-evangelism+get-192@lists.php.net to get a copy of this message | ||
Gabor Hojtsy wrote:
Anyway, hey, it's just a suggestion. Nothing will probably come of it anyway - no big deal. As far as user-agent implementation is concerned, it's not about implementation as it is about standards. The idea being that the standards cater for implementations both now and in the future - and if you're worried about the now, it's already implemented in netscape/mozilla - goodness knows how many other user agents we havn't even thought of are using it. You can't be talking about the 2 or 3 link tags? It's not like it's gonna make any difference to page load times - people spend more kb on comments (which are ignored by the user agent). As far as the [implementation specific] bar [in netscape/mozilla] is concerned - it is indeed *optional*. Not only that, mozilla/netscape has an option for it only to show up if neccesary - it's called "show only as needed". So you can't be talking about screen real-estate. What the hell *are* you talking about?http://www.w3.org/TR/html4/types.html#type-links Currently the www.php.net site does not use the link tag in a language context. While on on the point, the documentation could make excellent usage of some of the other rel types listed in the above link. specifically, "next", "prev", and "top". Different types of user agenets will make usage of these for different reasons (eg, a hand-held device with dedicated next/previous buttons). Look no further than Mozilla/Netscape7 VIEW: SHOW/HIDE: SITE NAVIGATION BARIMHO we would just make that page bigger with this addition, as not too many users utilize this functionality... I may be wrong though... Anyway do YOU use that toolbar? Goba You gotta be kidding me? This is small enhancement but it's a worthwhile one because it doesn't require much change, and has no side-effects (unless you're gonna make up a story about increased load times) - it improves accessibility for now and in the future. How the hell is it making the page bigger?