Re: [Trinidad] Skining - strange default value in: base-desktop.xss

Hello Cristi, I had that discussion a while back during incubation. I would also like a very light (empty) base skin and we're actually going to make one for a project. It's already possible by extending simple, overriding every single selectors and add a "-tr-inhibit: all;", effectively disabling

[jira] Created: (TRINIDAD-622) TrNumberConverter inserts thousand separator incorrectly for negative numbers

TrNumberConverter inserts thousand separator incorrectly for negative numbers - Key: TRINIDAD-622 URL: https://issues.apache.org/jira/browse/TRINIDAD-622 Project: MyFaces Trin

Re: [Trinidad] Skining - strange default value in: base-desktop.xss

I've a hunch this was added long, long ago by someone attempting to make IE match another browser (possibly even Netscape 4). I agree it's bizarre and should be deleted. -- Adam On 8/9/07, Cristi Toth <[EMAIL PROTECTED]> wrote: > Hi! > > I found a strange default value for IE browser: body { mar

Re: [Trinidad] Skining - strange default value in: base-desktop.xss

Ok... I thought that using a skin that extends no base skin or a very basic (empty) one would do the trick But I found out that the most basic one is the SimpleDesktopSkin which includes that huge base-desktop.xss I can understand that it is ok to have a good default skin But shouldn't it be a way

Re: [Trinidad] Skining - strange default value in: base-desktop.xss

My problem is even bigger :( as Simon Lessard already noticed in StyleSheetDocument, on line 477 the method: private StyleNode _resolveStyle(...) is really buggy The problem is that it takes all the style definitions of a selector / element in a 'random' order and the properties in the first inst

[Trinidad] Skining - strange default value in: base-desktop.xss

Hi! I found a strange default value for IE browser: body { margin-top: 8px } in base-desktop.xss on line 3943: 8px ... Why on earth would anybody need this setting? I lost some valuable time on finding this... And its effect was really annoying

[jira] Updated: (MYFACES-1701) The state gets reconstructed twice.

[ https://issues.apache.org/jira/browse/MYFACES-1701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bernhard Huemer updated MYFACES-1701: - Status: Patch Available (was: Open) > The state gets reconstructed twice. > --

[jira] Created: (MYFACES-1701) The state gets reconstructed twice.

The state gets reconstructed twice. --- Key: MYFACES-1701 URL: https://issues.apache.org/jira/browse/MYFACES-1701 Project: MyFaces Core Issue Type: Bug Affects Versions: 1.2.1-SNAPSHOT Reporter

[jira] Created: (TOBAGO-464) Create a real tx extension taglib for facelets

Create a real tx extension taglib for facelets -- Key: TOBAGO-464 URL: https://issues.apache.org/jira/browse/TOBAGO-464 Project: MyFaces Tobago Issue Type: Improvement Components: Facelet

Re: [Skinning] independent MyFaces skinning module

well, I used a ViewHandler which initialized the skinning but Martin told me that for PPR rendering purposes I should do it from the renderers and I'm not using a Filter (like the trinidad filter) I'm really busy these days, but I'll do my best to finish it until next week and post it somewhere r

[jira] Resolved: (TRINIDAD-621) af|inputDate::content is being used by both the popup calendar and the date field

[ https://issues.apache.org/jira/browse/TRINIDAD-621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Lessard resolved TRINIDAD-621. Resolution: Fixed Applied the fix to the JSF 1.1 trunk. Will probably be merged with the

[jira] Created: (TRINIDAD-621) af|inputDate::content is being used by both the popup calendar and the date field

af|inputDate::content is being used by both the popup calendar and the date field - Key: TRINIDAD-621 URL: https://issues.apache.org/jira/browse/TRINIDAD-621 Project: MyF

[jira] Updated: (TRINIDAD-145) ClassCastException when binding number-grouping-separator

[ https://issues.apache.org/jira/browse/TRINIDAD-145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeanne Waldman updated TRINIDAD-145: Resolution: Fixed Status: Resolved (was: Patch Available) New Revision: 564247 o

[jira] Resolved: (TOBAGO-460) Markup attribute for label

[ https://issues.apache.org/jira/browse/TOBAGO-460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bernd Bohmann resolved TOBAGO-460. -- Resolution: Fixed Thanks for your help :-) > Markup attribute for label >

[jira] Resolved: (TOBAGO-463) ActionListenerImpl should not catch AbortProcessingException

[ https://issues.apache.org/jira/browse/TOBAGO-463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Volker Weber resolved TOBAGO-463. - Resolution: Fixed > ActionListenerImpl should not catch AbortProcessingException > --

[jira] Created: (TOBAGO-463) ActionListenerImpl should not catch AbortProcessingException

ActionListenerImpl should not catch AbortProcessingException Key: TOBAGO-463 URL: https://issues.apache.org/jira/browse/TOBAGO-463 Project: MyFaces Tobago Issue Type: Bug Affec

Re: [TRINIDAD] Uncompressed JavaScript-Files

I very much agree about the DISABLE_CONTENT_COMPRESSION being a public api. It is extremely useful for skinning. I used to be reluctant to tell people about it since it was in impl, but it is nearly impossible to do without, and I find myself telling everyone that asks about skinning. It's espe

[jira] Commented: (TOBAGO-460) Markup attribute for label

[ https://issues.apache.org/jira/browse/TOBAGO-460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12518694 ] Helmut Swaczinna commented on TOBAGO-460: - Thanks, it works. > Markup attribute for label >

[jira] Created: (TRINIDAD-620) Client Side Date Restriction: to long error messages

Client Side Date Restriction: to long error messages Key: TRINIDAD-620 URL: https://issues.apache.org/jira/browse/TRINIDAD-620 Project: MyFaces Trinidad Issue Type: Bug Reporte