[JBoss JIRA] (RF-13096) focus: component loses focus on every second request when placed in Accordion, CollapsiblePanel or TabPanel
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13096?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13096:
-------------------------------
Fix Version/s: 5-Tracking
> focus: component loses focus on every second request when placed in Accordion, CollapsiblePanel or TabPanel
> -----------------------------------------------------------------------------------------------------------
>
> Key: RF-13096
> URL: https://issues.jboss.org/browse/RF-13096
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-misc
> Affects Versions: 4.3.0.Final, 4.3.3
> Environment: RichFaces 4.3.0.Final
> Metamer 4.3.0.20130130-Final
> JBoss AS 7.1.1.Final
> OpenJDK Runtime Environment 1.7.0_03-mockbuild_2013_06_05_13_14-b00 @ Linux
> Firefox 21.0 @ Linux x86_64
> Reporter: Jiří Štefek
> Fix For: 5.0.0.Alpha4, 5-Tracking
>
>
> Works with RF5.
> Stack:
> {code}
> 10:03:49,118 SEVERE [org.richfaces.log.Context] (http--127.0.0.1-8080-11) containerItem3: java.lang.IllegalArgumentException: containerItem3
> at javax.faces.component.UIComponentBase.findComponent(UIComponentBase.java:606) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
> at org.richfaces.renderkit.util.RendererUtils.findComponentFor(RendererUtils.java:759) [richfaces-components-ui-4.3.3.Final.jar:4.3.3.Final]
> at org.richfaces.renderkit.focus.AbstractFocusRenderStrategy.getFocusedComponent(AbstractFocusRenderStrategy.java:91) [richfaces-components-ui-4.3.3.Final.jar:4.3.3.Final]
> at org.richfaces.renderkit.focus.AbstractFocusRenderStrategy.getSubmittedFocus(AbstractFocusRenderStrategy.java:79) [richfaces-components-ui-4.3.3.Final.jar:4.3.3.Final]
> at org.richfaces.renderkit.focus.AbstractFocusRenderStrategy.getFocusCandidates(AbstractFocusRenderStrategy.java:40) [richfaces-components-ui-4.3.3.Final.jar:4.3.3.Final]
> at org.richfaces.renderkit.focus.AbstractFocusRenderStrategy.getFocusCandidatesAsString(AbstractFocusRenderStrategy.java:24) [richfaces-components-ui-4.3.3.Final.jar:4.3.3.Final]
> at org.richfaces.renderkit.focus.FormFocusRenderStrategy.getFocusCandidatesAsString(FormFocusRenderStrategy.java:65) [richfaces-components-ui-4.3.3.Final.jar:4.3.3.Final]
> at org.richfaces.renderkit.FocusRendererBase.getFocusCandidatesAsString(FocusRendererBase.java:38) [richfaces-components-ui-4.3.3.Final.jar:4.3.3.Final]
> at org.richfaces.renderkit.html.FocusRenderer.doEncodeEnd(FocusRenderer.java:91) [richfaces-components-ui-4.3.3.Final.jar:4.3.3.Final]
> at org.richfaces.renderkit.RendererBase.encodeEnd(RendererBase.java:175) [richfaces-components-ui-4.3.3.Final.jar:4.3.3.Final]
> at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:875) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
> at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
> at org.richfaces.context.ExtendedPartialViewContextImpl$RenderVisitCallback.visit(ExtendedPartialViewContextImpl.java:557) [richfaces-core-impl-4.3.3.Final.jar:4.3.3.Final]
> at org.richfaces.context.RenderExtendedVisitContext.invokeVisitCallbackForImplicitComponent(RenderExtendedVisitContext.java:70) [richfaces-core-impl-4.3.3.Final.jar:4.3.3.Final]
> at org.richfaces.context.BaseExtendedVisitContext.invokeVisitCallback(BaseExtendedVisitContext.java:333) [richfaces-core-impl-4.3.3.Final.jar:4.3.3.Final]
> at javax.faces.component.UIComponent.visitTree(UIComponent.java:1612) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
> at javax.faces.component.UIComponent.visitTree(UIComponent.java:1623) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
> at org.richfaces.component.AbstractTogglePanel.visitTree(AbstractTogglePanel.java:924) [richfaces-components-ui-4.3.3.Final.jar:4.3.3.Final]
> at javax.faces.component.UIComponent.visitTree(UIComponent.java:1623) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
> at javax.faces.component.UIForm.visitTree(UIForm.java:371) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
> at javax.faces.component.UIComponent.visitTree(UIComponent.java:1623) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
> at javax.faces.component.UIComponent.visitTree(UIComponent.java:1623) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
> at javax.faces.component.UIComponent.visitTree(UIComponent.java:1623) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
> at org.richfaces.context.ExtendedPartialViewContextImpl.processPartialRenderPhase(ExtendedPartialViewContextImpl.java:310) [richfaces-core-impl-4.3.3.Final.jar:4.3.3.Final]
> at org.richfaces.context.ExtendedPartialViewContextImpl.processPartial(ExtendedPartialViewContextImpl.java:213) [richfaces-core-impl-4.3.3.Final.jar:4.3.3.Final]
> at javax.faces.component.UIViewRoot.encodeChildren(UIViewRoot.java:981) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
> at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1779) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
> at com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:391) [jsf-impl-2.1.7-jbossorg-2.jar:]
> at com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:125) [jsf-impl-2.1.7-jbossorg-2.jar:]
> at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:288) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
> at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:288) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
> at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:121) [jsf-impl-2.1.7-jbossorg-2.jar:]
> at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) [jsf-impl-2.1.7-jbossorg-2.jar:]
> at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) [jsf-impl-2.1.7-jbossorg-2.jar:]
> at javax.faces.webapp.FacesServlet.service(FacesServlet.java:594) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:]
> at org.richfaces.tests.metamer.TestIdentityFilter.doFilter(TestIdentityFilter.java:93) [classes:]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:]
> at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.13.Final.jar:]
> at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final]
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.13.Final.jar:]
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.13.Final.jar:]
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.13.Final.jar:]
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.13.Final.jar:]
> at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25]
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 3 months
[JBoss JIRA] (RF-13018) a4j:commandButton wrong actions performed
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13018?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13018:
-------------------------------
Fix Version/s: 5-Tracking
(was: 5.0.0.Alpha4)
> a4j:commandButton wrong actions performed
> -----------------------------------------
>
> Key: RF-13018
> URL: https://issues.jboss.org/browse/RF-13018
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-a4j-core
> Affects Versions: 4.2.3.Final, 4.3.2
> Environment: Server: Fedora 17, Jboss AS 7.1.1.Final, Jboss EAP 6.1.0.Beta, Java 1.7.0_15
> Browsers: Chrome 26 and Chrome 27 on (Linux & Windows 7), Firefox 20.0 (Linux & Windows 7), IE 9
> Reporter: Rob Hare
> Assignee: Brian Leathem
> Fix For: 5-Tracking
>
> Attachments: RF-13018.zip
>
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> When an a4j commponent (a4j:commandButton, a4j:jsFunction) is activated, actions of other a4j:commandButtons on the page with type=button will be fired.
> For example, pressing either button in the following code will cause both richBean.function1() and richBean.function2() actions.
> {noformat}
> <h:form id="testForm">
> <a4j:commandButton id="button1" type="button" value="Button 1"
> action="#{richBean.function1}" />
> <a4j:commandButton id="button2" type="button" value="Button 2"
> action="#{richBean.function2}" />
> </h:form>
> {noformat}
> Note, if one of the a4j:commandButton is marked immediate, then only one action (possibly the wrong action) will be performed and block others. For instance if an a4j:jsFunction action was being triggered, the a4j:commandButton action may occur making appear that the a4j:jsFunction failed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 3 months
[JBoss JIRA] (RF-12977) a4j:queue breaks tabPanel
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12977?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-12977:
-------------------------------
Fix Version/s: 5-Tracking
(was: 5.0.0.Alpha4)
> a4j:queue breaks tabPanel
> -------------------------
>
> Key: RF-12977
> URL: https://issues.jboss.org/browse/RF-12977
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-output
> Affects Versions: 4.3.2, 5.0.0.Alpha2
> Environment: This happens in RF 4.3.2.CR1, but I can't select such version in JIRA.
> Reporter: Bernard Labno
> Priority: Critical
> Fix For: 5-Tracking
>
>
> There is clearly a bug in tabPanel.js
> {code}
> execAjax : function (oldPanel, newPanel) {
> var options = $.extend({}, newPanel.getTogglePanel().options["ajax"], {});
> this.__setActiveItem(newPanel);
> rf.ajax(newPanel.id, null, options);
> if (oldPanel) { // HERE IS THE BUG
> this.__setActiveItem(oldPanel);
> }
> return false;
> },
> {code}
> If the tab panel works in ajax mode and we attach a4j:queue with requestDelay="1000" then rf.ajax... will just add request to queue, but meanwhile the active item will be changed to old value.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 3 months
[JBoss JIRA] (RF-12270) Allow RichFaces to bring new CSS/JS resources into the page after AJAX request
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12270?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-12270:
-------------------------------
Fix Version/s: 5-Tracking
(was: 5.0.0.Alpha4)
> Allow RichFaces to bring new CSS/JS resources into the page after AJAX request
> ------------------------------------------------------------------------------
>
> Key: RF-12270
> URL: https://issues.jboss.org/browse/RF-12270
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: core, resource handling
> Affects Versions: 4.2.2.Final
> Reporter: Tomasz Kurpios
> Fix For: 5-Tracking
>
> Original Estimate: 2 days
> Remaining Estimate: 2 days
>
> Quoting the extract from official documentation (3.5 Restrictions):
> ??JSF 2 does not allow resources such as JavaScript or Cascading Style Sheets (CSS) to be added if the element requiring the resource is not initially present in the JSF tree. As such, components added to the tree via Ajax must have any required resources already loaded. In RichFaces, any components added to the JSF tree should have components with corresponding resources included on the main page initially. To facilitate this, components can use the rendered="false" setting to not be rendered on the page.??
>
> Setting rendered="false" is OK when components are in the tree. However, if there are lots of components on a single view, for performance reasons some parts might be excluded by means of <c:if> or <c:choose> tags.
> That's at least what could be done in 3.3.3. It worked fine back then. However, the JSF2 AJAX mechanism does not support this feature. This makes usage of aforementioned tags impossible in some cases.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 3 months
[JBoss JIRA] (RF-13127) onvalid and oninvalide pass wrong element when using rich:element with String field
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13127?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13127:
-------------------------------
Fix Version/s: 5-Tracking
(was: 5.0.0.Alpha4)
> onvalid and oninvalide pass wrong element when using rich:element with String field
> -----------------------------------------------------------------------------------
>
> Key: RF-13127
> URL: https://issues.jboss.org/browse/RF-13127
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-validators
> Affects Versions: 4.3.3
> Reporter: Louis Parisi
> Labels: testcase_provided
> Fix For: 5-Tracking
>
> Attachments: JSFTemplate.zip, RF-13127.zip, richfaces.zip
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> I have a bean iterated in a datatable. Using the rich:validator on fields in the bean I am executing javascript when a field is validated and apply styling based on valid or invalid state. The code below returns the correct element when the underlying field is a BigDecimal but intermittently returns the element from row zero and sometimes another rown when the field is a String. If I just reference a String vs. BigDecimal and display the element passed to the javascript I get form:myTable:4:myField for a BigDecimal field and always form:myTable:0:myField no matter the row for a String field.
> {code}
> <h:inputText id="vendor" value="#{car.vendor}" valueChangeListener="#{car.valueChanged}">
> <rich:validator oninvalid="valueModified(#{rich:element('vendor')}, false)"
> onvalid="valueModified(#{rich:element('vendor')}, true)"/>
> </h:inputText>
> {code}
> {code}
> <script>
> function valueModified(element, valid) {
> // use element.style rather than jQuery as it
> // does not set entire background
> alert("valueModified: " + element.id + " | valid: " + valid);
> element.style.background='yellow';
> if (valid) {
> jQuery(element).css("border-color", "lightgray");
> } else {
> jQuery(element).css("border-color", "red");
> }
> }
> </script>
> {code}
> Some other tests I did while trying to debug are:
> * I passed the rowKeyVar to a javascript method in the onvalid event and it passed the correct row for a BigDecimal and always zero for a String field.
> * The oncomplete event of the validator does not seem to fire for a String field but does for a BigDecimal field.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 3 months
[JBoss JIRA] (RF-11090) rich:collapsibleSubTable cannot be nested
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-11090?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-11090:
-------------------------------
Fix Version/s: 5-Tracking
(was: 5.0.0.Alpha4)
> rich:collapsibleSubTable cannot be nested
> -----------------------------------------
>
> Key: RF-11090
> URL: https://issues.jboss.org/browse/RF-11090
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.0.0.Final
> Reporter: Val Blant
> Priority: Minor
> Fix For: 5-Tracking
>
> Original Estimate: 45 minutes
> Remaining Estimate: 45 minutes
>
> When _<rich:collapsibleSubTable />_ s are nested, the following error occurs:
> {quote}
> This page contains the following errors:
> error on line 202 at column 74: Opening and ending tag mismatch: tbody line 0 and tr
> Below is a rendering of the page up to the first error.
> {quote}
> The page is rendered up to the nested _<rich:collapsibleSubTable />_.
> This error happens b/c nested sub tables render an extra _</tr>_ element after the nested subtable row.
> I was able to work around the problem by making a small tweak to _CollapsibleSubTableRenderer_. The lines I added or changes are marked with *"// fix line"* comment.
> {code:title=FixedCollapsibleSubTableRenderer.java|borderStyle=solid}
> /**
> * Allows nested subTables to be rendered properly
> */
> @ResourceDependencies({
> @ResourceDependency(name = "jquery.js"),
> @ResourceDependency(name = "richfaces.js"),
> @ResourceDependency(library="org.richfaces", name = "collapsible-subtable.ecss"),
> @ResourceDependency(library="org.richfaces", name = "collapsible-subtable.js")
> })
> public class FixedCollapsibleSubTableRenderer extends CollapsibleSubTableRenderer {
>
> @Override
> public void encodeRow(ResponseWriter writer, FacesContext facesContext, RowHolderBase holder) throws IOException {
> RowHolder rowHolder = (RowHolder)holder;
> Row row = rowHolder.getRow();
> putRowStylesIntoContext(facesContext, rowHolder);
> rowHolder.setRowStart(true);
> Iterator<UIComponent> components = row.columns();
> if (rowHolder.isUpdatePartial()) {
> partialStart(facesContext,((AbstractCollapsibleSubTable) row).getRelativeClientId(facesContext) + ":b");
> }
>
> int columnNumber = 0;
> boolean isSubtable = false; // fix line
> while (components.hasNext()) {
> UIComponent component = components.next();
> if(component.isRendered()) {
> if(component instanceof UIColumn ) {
> component.getAttributes().put(COLUMN_CLASS, getColumnClass(rowHolder, columnNumber));
> encodeColumn(facesContext, writer, (UIColumn)component , rowHolder);
> columnNumber++;
> } else if (component instanceof AbstractCollapsibleSubTable) {
> if(component.isRendered()) {
> isSubtable = true; // fix line
> encodeRowEnd(writer);
> }
>
> if ( ((AbstractCollapsibleSubTable) component).isExpanded() ) {
> component.encodeAll(facesContext);
> }
> rowHolder.setRowStart(true);
> }
> }
> }
> if ( !isSubtable) encodeRowEnd(writer); // fix line
> if (rowHolder.isUpdatePartial()) {
> partialEnd(facesContext);
> }
> }
> }
> {code}
> This renderer needs to be registered in _faces-config.xml_:
> {code}
> <render-kit>
> <renderer>
> <component-family>org.richfaces.Data</component-family>
> <renderer-type>org.richfaces.CollapsibleSubTableRenderer</renderer-type>
> <renderer-class>bla.FixedCollapsibleSubTableRenderer</renderer-class>
> </renderer>
> </render-kit>
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 3 months
[JBoss JIRA] (RF-13521) Remove Reference Data from Component Reference
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13521?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13521:
-------------------------------
Fix Version/s: 5-Tracking
(was: 5.0.0.Alpha4)
> Remove Reference Data from Component Reference
> ----------------------------------------------
>
> Key: RF-13521
> URL: https://issues.jboss.org/browse/RF-13521
> Project: RichFaces
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: doc
> Affects Versions: 5.0.0.Alpha1
> Reporter: Lukáš Fryč
> Fix For: 5-Tracking
>
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> See [Forum Reference].
> ----
> I have noticed each of the components in Component Reference contains reference data:
>
>
> {code}
> 3.5.2. Reference data
>
> component-type: org.richfaces.CommandLink
> component-class: org.richfaces.component.UICommandLink
> component-family: javax.faces.Command
> renderer-type: org.richfaces.CommandLinkRenderer
> {code}
>
> Similarly, VDL doc contains same information:
>
> {code}
> Tag Information
> Component type org.richfaces.CommandLink
> Tag Name a4j:commandLink
> Renderer Type org.richfaces.CommandLinkRenderer
> Handler Class None
> {code}
>
>
> The advantage of VDL doc is that it is automatically generated and so it doesn't need to be updated manually everytime something is changed.
>
> On the other hand, those are also not information which are used regularly - they are intented for advanced users and use cases.
>
> Thus I suggest to remove the Reference Data from Components Reference.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 3 months