[JBoss JIRA] (RF-12194) Support conditionnal resource dependency
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12194?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-12194:
-------------------------------
Fix Version/s: 4.3.0.Milestone1
> Support conditionnal resource dependency
> ----------------------------------------
>
> Key: RF-12194
> URL: https://issues.jboss.org/browse/RF-12194
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: cdk
> Affects Versions: 4.2.1.Final
> Environment: All
> Reporter: Paul Dijou
> Labels: dependency, resource, richfaces
> Fix For: 4.3.0.Milestone1
>
>
> Sometimes, when developping a component, you will need some resources only in particular case. For example, Bootstrap navbar only need Bootstrap CSS by default. But if you want to enable a collapse effect on smartphone in order to save space, you will also need bootstrap-collapse.js file.
> I'm fine with always having the JS file imported, but it would be more perfect if the resource dependency was resolved only if the collapse effect has been enabled in the navbar. So having a way to condition the import of some resource dependency.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] Created: (RF-10833) rich:tooltip doesn't work inside h:outputText
by Rene O (JIRA)
rich:tooltip doesn't work inside h:outputText
---------------------------------------------
Key: RF-10833
URL: https://issues.jboss.org/browse/RF-10833
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.0.0.Final
Environment: richfaces-4.0.0.Final, myfaces-2.0.5-SNAPSHOT, mojarra-2.1.1-b03,tomcat-7.0.11
Reporter: Rene O
If I use rich:tooltip inside h:outputText it doesn't show up. But inside a commandlink it works for example.
This doesn't work:
<h:outputText value="testvalue" >
<rich:tooltip>testtooltiptext</rich:tooltip>
</h:outputText>
But this works:
<a4j:commandLink value="testlink" ...>
<rich:tooltip>testtooltiptext</rich:tooltip>
</a4j:commandLink>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (RF-11741) ECSS parser is too aggressive when encountering non-standard CSS properties: selector omitted entirely
by Karsten Wutzke (Created) (JIRA)
ECSS parser is too aggressive when encountering non-standard CSS properties: selector omitted entirely
------------------------------------------------------------------------------------------------------
Key: RF-11741
URL: https://issues.jboss.org/browse/RF-11741
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: skinning
Affects Versions: 4.1.0.CR1
Reporter: Karsten Wutzke
Fix For: 4.1.0.Final
When defining rules like
{code}
.shadow
{
-webkit-box-shadow: 4px 4px 5px '#{richSkin.additionalBackgroundColor}';
-moz-box-shadow: 4px 4px 5px '#{richSkin.additionalBackgroundColor}';
box-shadow: 4px 4px 5px '#{richSkin.additionalBackgroundColor}';
}
{code}
in an ECSS file to create skin-dependent drop shadows, RF 4 will omit the above rule entirely and no shadows will be rendered. BTW it would be better to just omit the invalid properties instead of the entire selector (box-shadow: ... alone works).
Most browsers don't support the box-shadow yet, so defining proprietary properties *must* be possible. Note, this applies to a lot more properties than the above.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months