Patrick Moore wrote:
Hi there --
I am trying to access my tapestry 4.1.2 application via a fairly high-end
phone browser. (Samsung a900m). I have some preliminary results and a few
gotcha's posted on my blog at :
http://www.sworddance.com/blog/2007/02/09/phone-usability-design-notes-part-1/
Yep, quite interesting results you got there.
The general fallback plan for such situations is making sure the site
works with javascript disabled:
- Tapestry has good support for this, i.e. ajax components downgrade to
normal ones. BUT there exist some
javascript-only components and they're such by design. The most popular
of those are LinkSubmit and
contrib:Palette... they simply don't work without javascript. The new
autocompleter and data/time pickers also
fail but i have some plans for them :)
But what happens when devices don't have 100% browser-like javascript
support?
- Well, one might like to dynamically instruct Tapestry to not generate
any JS (which is not
currently possible), or (as you did) find and report the problems.
Now, i'm not aware if the javascript protocol (used in a link's href) is
a standard and accepted protocol
but when choosing from
<a href="javascript:doSomething()> or
<a href="#" onclick="doSomething()">
I now prefer (and would like to promote) the simple <a href="#"> and
wiring up the event afterwards.
I don't think this would break anything - perhaps Jesse could comment here.
Biggest gotcha so far is @LinkSubmit. LinkSubmit completely breaks in the
phone browser.
I also noticed that, see:
https://issues.apache.org/jira/browse/TAPESTRY-1245
-Pat Moore
--
Andreas Andreou - [EMAIL PROTECTED] - http://andyhot.di.uoa.gr
Tapestry / Tacos developer
Open Source / J2EE Consulting
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
