Hi,
The point of this would not be a recommended cross browser artifact
but in a sense a way to deal with situations like mobile phone version
of a site witch sometimes needs be very simple comparing with PC
browsers. In such situations such fragile approach would be quite
handy (as I hit some
In the case of large swaths of a site being different, I'd opt for URL
re-writing to send the WAP device to a parallel set of URLs.
On Mon, Sep 29, 2008 at 1:32 PM, Marius [EMAIL PROTECTED] wrote:
Hi,
The point of this would not be a recommended cross browser artifact
but in a sense a way
Am I being dumb here - could we not just run some checks on the user-
agent header and respond appropriately?
It would be very cool if SHtml was browser aware.
Cheers
Tim
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Browser detection is a really bad idea, and I would recommend avoiding
it at all costs. A much better solution is object detection.
Here's one pretty good description about why this is so:
http://developer.apple.com/internet/webcontent/objectdetection.html
Here's another:
Charles ... this is not only about JS level. One may simply click a
link or submit a simple form (with NO JS involved) and lift should
probably be aware of browser type it can correct some browser specific
idiosyncrasies in the resulting markup. Certain applications may need
for instance to
On Fri, Sep 26, 2008 at 12:15 PM, Charles F. Munat [EMAIL PROTECTED] wrote:
Ah, I forgot that you were talking server-side. Hmm. I'll have to think
about this.
For mobile browsers, are you talking ones that use WML? (Does anyone
still use that?) For something like that, I think you could
It would be nice to have some control over this. I work on a site
where we forward users to the iPhone version of the site when they
access / and their user agent matches the iPhone (or iPod Touch) user
agent. But, we also provide them with a link to view the full version
of the site.
This is
On Fri, Sep 26, 2008 at 2:16 AM, Tim Perrett [EMAIL PROTECTED] wrote:
Am I being dumb here - could we not just run some checks on the user-
agent header and respond appropriately?
It would be very cool if SHtml was browser aware.
Yes... that's what I'm suggesting. Right now, I think the
Not the most popular option out there but I generally detect IE6 from the
agent string and redirect to the Get Firefox page ;)
On Fri, Sep 26, 2008 at 3:51 AM, Marius [EMAIL PROTECTED] wrote:
Charles ... this is not only about JS level. One may simply click a
link or submit a simple form
Marius wrote:
+1.
So is anyone taking ownership on this? ... I could add this support
within a week or two maybe.
I'd rather you continue to work on the Record/Field stuff.
Can we get another taker on this project? Tyler... are you too busy
with the book? Jorge... got time? Someone
Cool.
On Sep 26, 7:40 pm, David Pollak [EMAIL PROTECTED] wrote:
Marius wrote:
+1.
So is anyone taking ownership on this? ... I could add this support
within a week or two maybe.
I'd rather you continue to work on the Record/Field stuff.
Can we get another taker on this project?
Tim Perrett wrote:
Hey guys,
Just a quick issue (or what seems to be an issue) that i've come
accross. If you do the following:
SHtml.submit(Register, save) % (type - image)
% (src - img/button-
submit-registration.gif)
For instance, it
jQuery has the jquery.browser and other user agent methods (under the
utilities section of the docs: http://docs.jquery.com/Utilities). If that's
not enough, there's this under the MIT license:
http://davecardwell.co.uk/javascript/jquery/plugins/jquery-browserdetect/
Derek
On Thu, Sep 25, 2008
Duh. I should stop posting before 7am.
On Thu, Sep 25, 2008 at 9:27 AM, David Pollak [EMAIL PROTECTED]
wrote:
On Thu, Sep 25, 2008 at 6:05 AM, Derek Chen-Becker [EMAIL PROTECTED]wrote:
jQuery has the jquery.browser and other user agent methods (under the
utilities section of the docs:
14 matches
Mail list logo
