Yeah there are many ways of dealing with such situations ... and URl rewriting is definitely one of them ... still it requires a bit of coding :) ... even the approach above would have been implemented through URL rewriters.
I'm not at all pushing for this as I don't have a strong case for it. Br's, Marius On Sep 29, 11:39 pm, "David Pollak" <[EMAIL PROTECTED]> wrote: > 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 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 walls in the past with other frameworks). > > > But never mind ... it was just a though not actually a full blown > > proposal. > > > Br's, > > Marius > > > On Sep 29, 7:24 pm, Tim Perrett <[EMAIL PROTECTED]> wrote: > > > IMHO, I wouldn't like this way of doing it. It seems too fragile. > > > Experience tells us that its usually only IE that has stupid quirks > > > (and will probably continue to do so), so I would see that level of > > > handling the browser issues to be problematic. > > > > Also, at a XHTML level, its often not possible to change the element > > > attributes - even today I added a class attribute to a SHtml.submit > > > placeholder and it was removed.... > > > > I would say we need to address two things: > > > > a) the wider issue of keeping tag-level attributes (e.g. classes and > > > id's) at tag level for designers / front end guys > > > b) providing server-side solutions for some of the stupid cross- > > > browser issues such as the image submit buttons. > > > > Thoughts? > > > > Cheers > > > > Tim > > > > On Sep 29, 4:55 pm, Marius <[EMAIL PROTECTED]> wrote: > > > > > If there is more room for an extra suggestion ... > > > > > As we know we're using prefixing for internationalization for instance > > > > let's say we have mypage.html. If we have mypage_es-ES.html lift will > > > > pick up the right markup per Locale. Perhaps we could also apply this > > > > for browsers like: > > > > > mypage_<LANG>_<COUNTRY>-<browser ID>.html > > > > > E.g. > > > > > mypage_es_ES-ie.html // applied for Spanish when using IE > > > > mypage_ar_SA-firefox.html // applied for SAudi Arabia when using > > > > Firefox > > > > > .. you got the idea. > > > > > Thoughts? (should be pretty easy to implement) > > > > > Br's, > > > > Marius > > > > > On Sep 26, 6:54 pm, "David Pollak" <[EMAIL PROTECTED]> > > > > wrote: > > > > > > 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 things we > > care > > > > > about on the server side are: > > > > > > - IE (and sometime just IE6) to deal with this image submit > > idiosyncrasy > > > > > and other places where IE has different mechanisms for achieving > > things than > > > > > do FF, Opera, and Safari/WebKit > > > > > - The iPhone (Android?) -- it'd be nice to choose different style > > sheets > > > > > based on these platforms... especially with a snippet > > > > > > I'd surface the browser detection in S (not SHtml). > > > > > > I'd also have snippets such as: > > > > > <lift:Browser if="IE6, Safari">.....</lift:Browser> > > > > > > <lift:Browser.choose> > > > > > <browser:ie6> > > > > > something > > > > > </browser:ie6> > > > > > > <browser:iphone> > > > > > Something just for the iphone > > > > > </browser:iphone> > > > > > </lift:Browser.choose> > > > > > > Thanks, > > > > > > David > > > > > > > Cheers > > > > > > > Tim > > > > > > -- > > > > > Lift, the simply functional web frameworkhttp://liftweb.net > > > > > Collaborative Task Managementhttp://much4.us > > > > > Follow me:http://twitter.com/dpp > > > > > Git some:http://github.com/dpp > > -- > Lift, the simply functional web frameworkhttp://liftweb.net > Collaborative Task Managementhttp://much4.us > Follow me:http://twitter.com/dpp > Git some:http://github.com/dpp --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---
