[ 
https://issues.apache.org/jira/browse/WOOKIE-131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13005931#comment-13005931
 ] 

Scott Wilson commented on WOOKIE-131:
-------------------------------------

OK, a couple of problems with JQuery Mobile, but I think fixable.

Basically, JQM assumes the widget is a top-level window, not an iframe, and 
this means there are a few bugs. Firefox and Chrome seem OK, but Safari has a 
problem with the "back" button not working - this can be fixed by changing 
"window.history.back()" to "self.history.back()" in JQM  - I've posted this on 
the JQM tracker so I'll see if this gets included. If not, we have to use a 
fork of JQM :-(

I've also seem an intermittent glitch with the fixed-position headers, and 
there are a slew of issue reports on those. It may be worth not bothering with 
fixed headers as the default.

> Skinnable widgets
> -----------------
>
>                 Key: WOOKIE-131
>                 URL: https://issues.apache.org/jira/browse/WOOKIE-131
>             Project: Wookie
>          Issue Type: Improvement
>            Reporter: Ross Gardler
>              Labels: mentor
>             Fix For: 0.9.1
>
>         Attachments: footer.txt
>
>
> One of the common problems with sites that consist of multiple widgets is 
> that they just luck messy. Each widget designer will create their own look 
> and feel and chaos ensues.
> Wookie should provide a facility to skin widgets in order to keep them 
> consistent on a single site. This requires:
> - design guidelines
> - common CSS
> - CSS override ability
> The design guidelines defines the recommended approach for designing a 
> widget. It will provide a template for common widget layouts and CSS 
> identifiers for common elements.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to