Using an User Agent switcher, you can see how some sites serve up
different content based on the user agent.
For a demonstration of making content accessible to different users, in
this case search engines such as Google, camouflage yourself with the
Googlebot UA and visit some Microsoft web pa
Nick Lo wrote:
> Here's how to enable it:
>
> http://www.macosxhints.com/article.php?story=20030110063041629
>
> However, before you get too excited "it can pretend to be a bunch of
> different browsers" merely refers to it's ability to set the User
> Agent HTTP header to say it's another browser.
Here's how to enable it:
http://www.macosxhints.com/article.php?story=20030110063041629
However, before you get too excited "it can pretend to be a bunch of
different browsers" merely refers to it's ability to set the User Agent
HTTP header to say it's another browser. Useful e.g. when online
What tha - how does this work?
On 04/02/2004, at 6:17 PM, Sean A Corfield wrote:
The debug menu is extremely useful: it can pretend to be a bunch of different browsers, it has a basic load test engine built in, it can show the DOM tree...
Peter Gifford
Universal HeadÂ
Design That Works.
7/43
On Mar 3, 2004, at 10:07 PM, [EMAIL PROTECTED] wrote:
Sorry, but why is everyone so enthused about safari?,
Because it's a very good, very fast browser. And it's very well
integrated with OS X. The debug menu is extremely useful: it can
pretend to be a bunch of different browsers, it has a basic
Sorry, but why is everyone so enthused about safari?,
After my frustrations I use Mozilla firebird.
http://www.mozilla.org/products/firebird/
okay, it is still in beta testing, but the beauty is that you can
become part of the development (over my head), but designers can
stylize it via the .jar f
Justin,
Perhaps Safari needs a developer edition
Nice idea. What I guess happens at present is that the "web kit" that
drives Safari, Mail (and iTunes?) is the important part of the update,
and this is something that is available system-wide. So there would
have to be a way of running different
On Feb 3, 2004, at 8:49 PM, Justin French wrote:
The problem is, Safari 1.0 doesn't actually expire (AFAIK).
Correct. 1.0 is the last version produced for OS X 10.2.x (Jaguar). 1.2
is the current version for OS X 10.3.x (Panther).
Whilst it's more than likely that a vast majority of web users wil
thanks for clarifying that justin.
I thought about my comment & realized that it is with os update that it
happens, so thanks for correcting me...
*
The discussion list for http://webstandardsgroup.org/
***
On Wednesday, February 4, 2004, at 03:03 PM, Universal Head wrote:
Now THAT's a smart idea - old browsers that expire. If only IE and NN
did that!
Peter
A browser that actually expires would be great. If NN4, IE4, Opera 4,
etc all *expired* in 2002, the cost of web development would be a lot
Now THAT's a smart idea - old browsers that expire. If only IE and NN
did that!
Peter
Safari V 1.2 Actually takes over the old safari which expires.
they are still having a few javascripting issues where some scripts
still wont work.
*
The di
Hi people, this is my first mail, I am very glad to become part of this
site, as It has raised
my awareness of compatabilities heaps!
Safari V 1.2 Actually takes over the old safari which expires.
they are still having a few javascripting issues where some scripts
still wont work.
I am usin
12 matches
Mail list logo