[jira] [Commented] (TOBAGO-1803) Make Tobago buildable and runnable with Java JDK 9
[ https://issues.apache.org/jira/browse/TOBAGO-1803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16182926#comment-16182926 ] Hudson commented on TOBAGO-1803: SUCCESS: Integrated in Jenkins build Tobago Trunk #1043 (See [https://builds.apache.org/job/Tobago%20Trunk/1043/]) TOBAGO-1803: Make Tobago buildable and runnable with Java JDK 9 * (lofwyr: rev b69409d0b71d76058dbdea8825d680935c32c879) * (edit) pom.xml * (edit) tobago-theme/pom.xml > Make Tobago buildable and runnable with Java JDK 9 > -- > > Key: TOBAGO-1803 > URL: https://issues.apache.org/jira/browse/TOBAGO-1803 > Project: MyFaces Tobago > Issue Type: Task > Components: Build, Core >Reporter: Udo Schnurpfeil >Assignee: Udo Schnurpfeil > Fix For: 4.0.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (TOBAGO-1723) tc:segmentLayout can't be direct child of tc:segmentLayout
[ https://issues.apache.org/jira/browse/TOBAGO-1723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16182925#comment-16182925 ] Hudson commented on TOBAGO-1723: SUCCESS: Integrated in Jenkins build Tobago Trunk #1043 (See [https://builds.apache.org/job/Tobago%20Trunk/1043/]) TOBAGO-1723: tc:segmentLayout can't be direct child of tc:segmentLayout (lofwyr: rev dc8660161f4564cd7a09500925c979eeb7380070) * (edit) tobago-core/src/main/java/org/apache/myfaces/tobago/internal/taglib/component/SegmentLayoutConstraintTagDeclaration.java * (edit) tobago-core/src/main/java/org/apache/myfaces/tobago/facelets/SegmentLayoutConstraintHandler.java * (edit) tobago-example/tobago-example-demo/src/main/webapp/content/30-concept/16-layout/30-segment/segment-layout.xhtml > tc:segmentLayout can't be direct child of tc:segmentLayout > -- > > Key: TOBAGO-1723 > URL: https://issues.apache.org/jira/browse/TOBAGO-1723 > Project: MyFaces Tobago > Issue Type: Bug > Components: Core >Reporter: Udo Schnurpfeil >Assignee: Udo Schnurpfeil >Priority: Minor > Fix For: 4.0.0 > > > There will be a ClassCastException. Use a between the tag as a > workaround. > Problem occurred only in 4.0.0-SNAPSHOT. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (TOBAGO-1795) Set Java Source to Java 8
[ https://issues.apache.org/jira/browse/TOBAGO-1795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16182924#comment-16182924 ] Hudson commented on TOBAGO-1795: SUCCESS: Integrated in Jenkins build Tobago Trunk #1043 (See [https://builds.apache.org/job/Tobago%20Trunk/1043/]) TOBAGO-1795: Set Java Source to Java 8 * remove unneeded explicit type (lofwyr: rev 9111da7f1b573c1e003aeaf2c5c4cd92c0baf689) * (edit) tobago-core/src/main/java/org/apache/myfaces/tobago/internal/behavior/EventBehavior.java * (edit) tobago-core/src/main/java/org/apache/myfaces/tobago/internal/renderkit/renderer/SuggestRenderer.java * (edit) tobago-core/src/test/java/org/apache/myfaces/tobago/internal/config/AbstractTobagoTestBase.java * (edit) tobago-core/src/main/java/org/apache/myfaces/tobago/context/TobagoBundle.java * (edit) tobago-example/tobago-example-data/src/main/java/org/apache/myfaces/tobago/example/data/SolarObject.java * (edit) tobago-core/src/main/java/org/apache/myfaces/tobago/internal/renderkit/renderer/SheetRenderer.java * (edit) tobago-example/tobago-example-demo/src/main/java/org/apache/myfaces/tobago/example/demo/PrettyUrlForMenuNavigationHandler.java * (edit) tobago-core/src/main/java/org/apache/myfaces/tobago/internal/component/AbstractUISheet.java > Set Java Source to Java 8 > - > > Key: TOBAGO-1795 > URL: https://issues.apache.org/jira/browse/TOBAGO-1795 > Project: MyFaces Tobago > Issue Type: Task > Components: Build >Reporter: Udo Schnurpfeil >Assignee: Udo Schnurpfeil > Fix For: 4.0.0 > > > This also implies the minimal runtime version to JDK 1.8 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MYFACES-4160) ViewState not written for Ajax request
[ https://issues.apache.org/jira/browse/MYFACES-4160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16183102#comment-16183102 ] Thomas Andraschko commented on MYFACES-4160: Checked that case again and i remember now that the forms were always rendered without viewstate id and was applied via JS. Now looking why it doesn't work - Somehow we also have 2 AjaxResponse.js. > ViewState not written for Ajax request > -- > > Key: MYFACES-4160 > URL: https://issues.apache.org/jira/browse/MYFACES-4160 > Project: MyFaces Core > Issue Type: Bug >Affects Versions: 2.3.0-beta >Reporter: Thomas Andraschko > Fix For: 2.3.0 > > > If you run the application from MYFACES-4156 via mvn jetty:run, the > viewStateId isn't rendered again after the first ajax request. > Seems like FaceletViewDeclerationLanguage line 1910 should handle that but it > skips. > [~lu4242] Could you please check that? -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (TOBAGO-1812) Revise flex layout manager:
[ https://issues.apache.org/jira/browse/TOBAGO-1812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16183036#comment-16183036 ] Hudson commented on TOBAGO-1812: SUCCESS: Integrated in Jenkins build Tobago Trunk #1044 (See [https://builds.apache.org/job/Tobago%20Trunk/1044/]) TOBAGO-1812: Revise flex layout manager: * use Bootstrap (lofwyr: rev ef348f86b533cc47a1ebb97b7cba00cf8e5bc2b3) * (edit) tobago-core/src/main/java/org/apache/myfaces/tobago/internal/taglib/component/FlexLayoutTagDeclaration.java * (edit) tobago-core/src/main/java/org/apache/myfaces/tobago/renderkit/css/TobagoClass.java * (edit) tobago-core/src/test/java/org/apache/myfaces/tobago/renderkit/css/TobagoClassUnitTest.java * (edit) tobago-core/src/main/java/org/apache/myfaces/tobago/renderkit/css/BootstrapClass.java * (edit) tobago-core/src/main/resources/scss/_tobago.scss * (edit) tobago-core/src/main/java/org/apache/myfaces/tobago/internal/renderkit/renderer/FlexLayoutRenderer.java > Revise flex layout manager: > --- > > Key: TOBAGO-1812 > URL: https://issues.apache.org/jira/browse/TOBAGO-1812 > Project: MyFaces Tobago > Issue Type: Task > Components: Core, Themes >Reporter: Udo Schnurpfeil >Assignee: Udo Schnurpfeil > Fix For: 4.0.0 > > > * use Bootstrap CSS classes, instead of our own > * check, if we can implement it, without using JavaScript > * in current SNAPSHOT there is a problem with
[jira] [Comment Edited] (MYFACES-4160) ViewState not written for Ajax request
[ https://issues.apache.org/jira/browse/MYFACES-4160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16183102#comment-16183102 ] Thomas Andraschko edited comment on MYFACES-4160 at 9/27/17 7:19 PM: - Checked that case again and i remember now that the forms were always rendered without viewstate id and was applied via JS. Now looking why it doesn't work - Somehow we also have 2 AjaxResponse.js. Seems like AjaxResponse.js instead AjaxResponse22.js is used, we definitely need a cleanup here. was (Author: tandraschko): Checked that case again and i remember now that the forms were always rendered without viewstate id and was applied via JS. Now looking why it doesn't work - Somehow we also have 2 AjaxResponse.js. > ViewState not written for Ajax request > -- > > Key: MYFACES-4160 > URL: https://issues.apache.org/jira/browse/MYFACES-4160 > Project: MyFaces Core > Issue Type: Bug >Affects Versions: 2.3.0-beta >Reporter: Thomas Andraschko > Fix For: 2.3.0 > > > If you run the application from MYFACES-4156 via mvn jetty:run, the > viewStateId isn't rendered again after the first ajax request. > Seems like FaceletViewDeclerationLanguage line 1910 should handle that but it > skips. > [~lu4242] Could you please check that? -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (TOBAGO-1812) Revise flex layout manager:
Udo Schnurpfeil created TOBAGO-1812: --- Summary: Revise flex layout manager: Key: TOBAGO-1812 URL: https://issues.apache.org/jira/browse/TOBAGO-1812 Project: MyFaces Tobago Issue Type: Task Components: Core, Themes Reporter: Udo Schnurpfeil Assignee: Udo Schnurpfeil * use Bootstrap CSS classes, instead of our own * check, if we can implement it, without using JavaScript * in current SNAPSHOT there is a problem with
[jira] [Resolved] (MYFACES-4159) Update FacesValidator and FacesBehavior annotations target
[ https://issues.apache.org/jira/browse/MYFACES-4159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eduardo Breijo resolved MYFACES-4159. - Resolution: Fixed Fix Version/s: 2.3.0 > Update FacesValidator and FacesBehavior annotations target > -- > > Key: MYFACES-4159 > URL: https://issues.apache.org/jira/browse/MYFACES-4159 > Project: MyFaces Core > Issue Type: Bug > Components: JSR-372 >Affects Versions: 2.3.0-beta >Reporter: Eduardo Breijo >Assignee: Eduardo Breijo >Priority: Minor > Fix For: 2.3.0 > > Attachments: MYFACES-4159.patch > > > The JSF 2.3 spec section 5.9.1 says that it must be possible to use @Inject > when specifying FacesConverters, FacesValidators and FacesBehaviors. On > MyFaces 2.3, only FacesConverters works fine when trying to inject them, but > FacesValidator and FacesBehavior annotations need to be updated to allow the > same target as FacesConverters so we don't get any compile issues. I'm going > to provide a patch for this. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Reopened] (MYFACES-4156) Myface is not showing the FacesMessage after validation when ValidatorException is thown.
[
https://issues.apache.org/jira/browse/MYFACES-4156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dora Rajappan reopened MYFACES-4156:
FacesMessage is not displayed for more than one wrong entries(eg password retry
max 3 attempts). This scenario is replicated with the project you have provided
as it is. FacesMessage is correctly displayed for the first wrong entry and not
for the subsequent entries unless page is refreshed.
> Myface is not showing the FacesMessage after validation when
> ValidatorException is thown.
> -
>
> Key: MYFACES-4156
> URL: https://issues.apache.org/jira/browse/MYFACES-4156
> Project: MyFaces Core
> Issue Type: Bug
>Affects Versions: 2.3.0-beta
>Reporter: Dora Rajappan
> Attachments: login.xhtml, MessageBean.java, mf23test.zip,
> MyValidator.java
>
>
> Myfaces 2.3 is not showing the FacesMessage after validation when
> ValidatorException is thrown. Same works with mojarra 2.2.
> if (param.length() > 32) {
> FacesMessage msg = new FacesMessage("Username should
> not exceed 32");
>
> throw new ValidatorException(msg);
> }
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (MYFACES-4156) Myface is not showing the FacesMessage after validation when ValidatorException is thown.
[
https://issues.apache.org/jira/browse/MYFACES-4156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16182178#comment-16182178
]
Thomas Andraschko commented on MYFACES-4156:
It's another bugs, seems like the viewstateid isn't rerendered after the first
ajax request.
> Myface is not showing the FacesMessage after validation when
> ValidatorException is thown.
> -
>
> Key: MYFACES-4156
> URL: https://issues.apache.org/jira/browse/MYFACES-4156
> Project: MyFaces Core
> Issue Type: Bug
>Affects Versions: 2.3.0-beta
>Reporter: Dora Rajappan
> Attachments: login.xhtml, MessageBean.java, mf23test.zip,
> MyValidator.java
>
>
> Myfaces 2.3 is not showing the FacesMessage after validation when
> ValidatorException is thrown. Same works with mojarra 2.2.
> if (param.length() > 32) {
> FacesMessage msg = new FacesMessage("Username should
> not exceed 32");
>
> throw new ValidatorException(msg);
> }
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (MYFACES-4160) ViewState not written for Ajax request
Thomas Andraschko created MYFACES-4160: -- Summary: ViewState not written for Ajax request Key: MYFACES-4160 URL: https://issues.apache.org/jira/browse/MYFACES-4160 Project: MyFaces Core Issue Type: Bug Affects Versions: 2.3.0-beta Reporter: Thomas Andraschko If you run the application from MYFACES-4156 via mvn jetty:run, the viewStateId isn't rendered again after the first ajax request. Seems like FaceletViewDeclerationLanguage line 1910 should handle that but it skips. [~lu4242] Could you please check that? -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (TOBAGO-1806) Allow vertical align for segment layout
Henning Noeth created TOBAGO-1806:
-
Summary: Allow vertical align for segment layout
Key: TOBAGO-1806
URL: https://issues.apache.org/jira/browse/TOBAGO-1806
Project: MyFaces Tobago
Issue Type: New Feature
Components: Core
Affects Versions: 3.0.6
Reporter: Henning Noeth
Have a look at:
https://getbootstrap.com/docs/4.0/layout/grid/#vertical-alignment
Possible solution:
{code:xml}{code}
Allowed values: top, center, bottom
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (MYFACES-4156) Myface is not showing the FacesMessage after validation when ValidatorException is thown.
[
https://issues.apache.org/jira/browse/MYFACES-4156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16182191#comment-16182191
]
Dora Rajappan commented on MYFACES-4156:
Yes I will open another bug then. It works with mojarra. Yes partial response
omits the h:messages.
> Myface is not showing the FacesMessage after validation when
> ValidatorException is thown.
> -
>
> Key: MYFACES-4156
> URL: https://issues.apache.org/jira/browse/MYFACES-4156
> Project: MyFaces Core
> Issue Type: Bug
>Affects Versions: 2.3.0-beta
>Reporter: Dora Rajappan
> Attachments: login.xhtml, MessageBean.java, mf23test.zip,
> MyValidator.java
>
>
> Myfaces 2.3 is not showing the FacesMessage after validation when
> ValidatorException is thrown. Same works with mojarra 2.2.
> if (param.length() > 32) {
> FacesMessage msg = new FacesMessage("Username should
> not exceed 32");
>
> throw new ValidatorException(msg);
> }
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (MYFACES-4156) Myface is not showing the FacesMessage after validation when ValidatorException is thown.
[
https://issues.apache.org/jira/browse/MYFACES-4156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16182193#comment-16182193
]
Thomas Andraschko commented on MYFACES-4156:
i already openend another bug:
https://issues.apache.org/jira/browse/MYFACES-4160
> Myface is not showing the FacesMessage after validation when
> ValidatorException is thown.
> -
>
> Key: MYFACES-4156
> URL: https://issues.apache.org/jira/browse/MYFACES-4156
> Project: MyFaces Core
> Issue Type: Bug
>Affects Versions: 2.3.0-beta
>Reporter: Dora Rajappan
> Attachments: login.xhtml, MessageBean.java, mf23test.zip,
> MyValidator.java
>
>
> Myfaces 2.3 is not showing the FacesMessage after validation when
> ValidatorException is thrown. Same works with mojarra 2.2.
> if (param.length() > 32) {
> FacesMessage msg = new FacesMessage("Username should
> not exceed 32");
>
> throw new ValidatorException(msg);
> }
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (TOBAGO-1807) Allow alignment on specific segments for segment layout
Henning Noeth created TOBAGO-1807:
-
Summary: Allow alignment on specific segments for segment layout
Key: TOBAGO-1807
URL: https://issues.apache.org/jira/browse/TOBAGO-1807
Project: MyFaces Tobago
Issue Type: New Feature
Components: Core
Affects Versions: 3.0.6
Reporter: Henning Noeth
Have a look at:
https://getbootstrap.com/docs/4.0/layout/grid/#vertical-alignment
Possible solution:
{code:xml}{code}
Allowed values: start, center, end
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (TOBAGO-1808) Allow horizontal alignment for segment layout
Henning Noeth created TOBAGO-1808:
-
Summary: Allow horizontal alignment for segment layout
Key: TOBAGO-1808
URL: https://issues.apache.org/jira/browse/TOBAGO-1808
Project: MyFaces Tobago
Issue Type: New Feature
Components: Core
Affects Versions: 3.0.6
Reporter: Henning Noeth
Have a look at:
https://getbootstrap.com/docs/4.0/layout/grid/#horizontal-alignment
Possible solution:
{code:xml}{code}
Allowed values: start, center, end, around, between
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (TOBAGO-1809) Ordering for segment layout
Henning Noeth created TOBAGO-1809:
-
Summary: Ordering for segment layout
Key: TOBAGO-1809
URL: https://issues.apache.org/jira/browse/TOBAGO-1809
Project: MyFaces Tobago
Issue Type: New Feature
Reporter: Henning Noeth
Have a look at: https://getbootstrap.com/docs/4.0/layout/grid/#flex-order
Possible solution:
{code:xml}{code}
Allowed values: 1 to 12
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (TOBAGO-1795) Set Java Source to Java 8
[ https://issues.apache.org/jira/browse/TOBAGO-1795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Udo Schnurpfeil resolved TOBAGO-1795. - Resolution: Fixed > Set Java Source to Java 8 > - > > Key: TOBAGO-1795 > URL: https://issues.apache.org/jira/browse/TOBAGO-1795 > Project: MyFaces Tobago > Issue Type: Task > Components: Build >Reporter: Udo Schnurpfeil >Assignee: Udo Schnurpfeil > Fix For: 4.0.0 > > > This also implies the minimal runtime version to JDK 1.8 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (TOBAGO-1791) There should be a "nonce" for each request to protect CSS with CSP
[ https://issues.apache.org/jira/browse/TOBAGO-1791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Udo Schnurpfeil resolved TOBAGO-1791. - Resolution: Fixed > There should be a "nonce" for each request to protect CSS with CSP > -- > > Key: TOBAGO-1791 > URL: https://issues.apache.org/jira/browse/TOBAGO-1791 > Project: MyFaces Tobago > Issue Type: New Feature > Components: Core >Reporter: Udo Schnurpfeil >Assignee: Udo Schnurpfeil >Priority: Minor > Fix For: 4.0.0 > > > The "nonce" allowes inline styling, so we don't need the data-tobago-style > attribute. > The "nonce" should also be usable inside the tobago-config.xml -> directive -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (TOBAGO-1792) CSP: using CSP Level 2 syntax
[ https://issues.apache.org/jira/browse/TOBAGO-1792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Udo Schnurpfeil resolved TOBAGO-1792. - Resolution: Fixed > CSP: using CSP Level 2 syntax > - > > Key: TOBAGO-1792 > URL: https://issues.apache.org/jira/browse/TOBAGO-1792 > Project: MyFaces Tobago > Issue Type: Improvement >Reporter: Udo Schnurpfeil >Assignee: Udo Schnurpfeil >Priority: Minor > Fix For: 4.0.0 > > > Renaming frame-src to child-src -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (TOBAGO-1698) Update some build libs
[ https://issues.apache.org/jira/browse/TOBAGO-1698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Udo Schnurpfeil resolved TOBAGO-1698. - Resolution: Fixed > Update some build libs > -- > > Key: TOBAGO-1698 > URL: https://issues.apache.org/jira/browse/TOBAGO-1698 > Project: MyFaces Tobago > Issue Type: Task >Reporter: Udo Schnurpfeil >Assignee: Udo Schnurpfeil >Priority: Minor > Fix For: 4.0.0 > > > * checkstyle -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (TOBAGO-1663) Clean up attic examples
[ https://issues.apache.org/jira/browse/TOBAGO-1663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Udo Schnurpfeil resolved TOBAGO-1663. - Resolution: Fixed > Clean up attic examples > --- > > Key: TOBAGO-1663 > URL: https://issues.apache.org/jira/browse/TOBAGO-1663 > Project: MyFaces Tobago > Issue Type: Task >Reporter: Udo Schnurpfeil >Assignee: Udo Schnurpfeil >Priority: Trivial > Fix For: 4.0.0 > > > There are some examples, which are not "state of the art". > The content is attic, but contain some interesting stuff. > * test > * addressbook > * portlet (currently not maintained actively) > The interesting stuff should be moved to the "demo" and the rest should be > removed. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (TOBAGO-1639) Tobago should work without creating a session
[ https://issues.apache.org/jira/browse/TOBAGO-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Udo Schnurpfeil resolved TOBAGO-1639. - Resolution: Fixed > Tobago should work without creating a session > - > > Key: TOBAGO-1639 > URL: https://issues.apache.org/jira/browse/TOBAGO-1639 > Project: MyFaces Tobago > Issue Type: Improvement > Components: Core >Reporter: Udo Schnurpfeil >Assignee: Udo Schnurpfeil > Fix For: 4.0.0 > > > So far, an HttpSession will created automatically. > (for non business applications, this is not reasonable) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (TOBAGO-1593) Markup to hide components on small displays
[ https://issues.apache.org/jira/browse/TOBAGO-1593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16182480#comment-16182480 ] Udo Schnurpfeil commented on TOBAGO-1593: - We should check how we implement this feature: # inside the layout managers # use # attributes of all tags # sub tag of all tags Currently my favorite is #1. > Markup to hide components on small displays > --- > > Key: TOBAGO-1593 > URL: https://issues.apache.org/jira/browse/TOBAGO-1593 > Project: MyFaces Tobago > Issue Type: New Feature >Affects Versions: 3.0.0-alpha-5 >Reporter: Matthias Wronka > Fix For: 4.1.0 > > > On small devices, it should be possible to limit the components that are > displayed to a Minimum . E.g. tables should be limited to the most necessary > columns. This could be achieved by CSS-classes, that hide columns at certain > display-sizes. > The definition could look like: > > ... > > The "hideFrom"-value uses the same steps as the segmentLayout. Whenever the > given responsive-breakpoint is reached, the component should be hidden. > Maybe this should be a generic Argument for (almost) any component because > it´s a generic problem. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (TOBAGO-1593) Markup to hide components on small displays
[ https://issues.apache.org/jira/browse/TOBAGO-1593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16182480#comment-16182480 ] Udo Schnurpfeil edited comment on TOBAGO-1593 at 9/27/17 12:31 PM: --- We should check how we implement this feature: # inside the layout managers # use # attributes of all tags # sub tag of all tags Currently my favorite is #1. was (Author: lofwyr): We should check how we implement this feature: # inside the layout managers # use # attributes of all tags # sub tag of all tags Currently my favorite is #1. > Markup to hide components on small displays > --- > > Key: TOBAGO-1593 > URL: https://issues.apache.org/jira/browse/TOBAGO-1593 > Project: MyFaces Tobago > Issue Type: New Feature >Affects Versions: 3.0.0-alpha-5 >Reporter: Matthias Wronka > Fix For: 4.1.0 > > > On small devices, it should be possible to limit the components that are > displayed to a Minimum . E.g. tables should be limited to the most necessary > columns. This could be achieved by CSS-classes, that hide columns at certain > display-sizes. > The definition could look like: > > ... > > The "hideFrom"-value uses the same steps as the segmentLayout. Whenever the > given responsive-breakpoint is reached, the component should be hidden. > Maybe this should be a generic Argument for (almost) any component because > it´s a generic problem. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (TOBAGO-1593) Markup to hide components on small displays
[ https://issues.apache.org/jira/browse/TOBAGO-1593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16182485#comment-16182485 ] Matthias Wronka commented on TOBAGO-1593: - Thumbs up for #1 > Markup to hide components on small displays > --- > > Key: TOBAGO-1593 > URL: https://issues.apache.org/jira/browse/TOBAGO-1593 > Project: MyFaces Tobago > Issue Type: New Feature >Affects Versions: 3.0.0-alpha-5 >Reporter: Matthias Wronka > Fix For: 4.1.0 > > > On small devices, it should be possible to limit the components that are > displayed to a Minimum . E.g. tables should be limited to the most necessary > columns. This could be achieved by CSS-classes, that hide columns at certain > display-sizes. > The definition could look like: > > ... > > The "hideFrom"-value uses the same steps as the segmentLayout. Whenever the > given responsive-breakpoint is reached, the component should be hidden. > Maybe this should be a generic Argument for (almost) any component because > it´s a generic problem. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (TOBAGO-1810) Create a markup for expanding tc:bar
Henning Noeth created TOBAGO-1810:
-
Summary: Create a markup for expanding tc:bar
Key: TOBAGO-1810
URL: https://issues.apache.org/jira/browse/TOBAGO-1810
Project: MyFaces Tobago
Issue Type: New Feature
Components: Core
Affects Versions: 3.0.6
Reporter: Henning Noeth
Assignee: Henning Noeth
Since Bootstrap Beta, needs a custom class set:
navbar-expand-{sm|md|lg|xl}
This should be done by markups.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (TOBAGO-1534) Some dependencies currently breaking CSP (Content Security Policy) in Tobago 3
[ https://issues.apache.org/jira/browse/TOBAGO-1534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Udo Schnurpfeil resolved TOBAGO-1534. - Resolution: Fixed Assignee: Udo Schnurpfeil Fix Version/s: 4.0.0 > Some dependencies currently breaking CSP (Content Security Policy) in Tobago 3 > -- > > Key: TOBAGO-1534 > URL: https://issues.apache.org/jira/browse/TOBAGO-1534 > Project: MyFaces Tobago > Issue Type: Bug > Components: Core, Themes >Reporter: Udo Schnurpfeil >Assignee: Udo Schnurpfeil > Fix For: 4.0.0 > > > Known Problems with CSP: > * Bootstrap 4: https://github.com/twbs/bootstrap/issues/17964 (/) > * MyFaces jsf.js calls "eval" > ** copy jsf.js to tobago-jsf.js to > *** work on removing "eval" > *** be independent of different implementations (there are problems with > MyFaces 2.0, which are fixed with the 2.2 jsf.js version) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (TOBAGO-919) Components should be resizable on the client side.
[ https://issues.apache.org/jira/browse/TOBAGO-919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16182510#comment-16182510 ] Udo Schnurpfeil commented on TOBAGO-919: I need a UserStory or something like that, for this feature. > Components should be resizable on the client side. > -- > > Key: TOBAGO-919 > URL: https://issues.apache.org/jira/browse/TOBAGO-919 > Project: MyFaces Tobago > Issue Type: New Feature > Environment: N/A >Reporter: Dom W. > > Dear all, > It would be a great improvement, if one could make (certain) components > resizable, such that the user can resize them in the browser. A similar > behavior is already available for tc:column. In particular I have the > following scenario in mind, which also caused me to submit this feature > request: A tc:box contains a tc:sheet with many rows. Now, the user should be > able to (vertically) enlarge the tc:box and thus giving the tc:sheet more > space to display the rows. > I hope this idea is not too vague and can be set into practice. > Thanks a lot for your answers and your work! > dw > P.S. For reference: As you certainly know, "PrimeFaces" has a "resizable" > component, that just seems to implement such a behavior (although I have > never used/tried it so far). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (TOBAGO-1811) Allow '*' and 'auto' segments for segment layout
Henning Noeth created TOBAGO-1811: - Summary: Allow '*' and 'auto' segments for segment layout Key: TOBAGO-1811 URL: https://issues.apache.org/jira/browse/TOBAGO-1811 Project: MyFaces Tobago Issue Type: New Feature Components: Core Affects Versions: 3.0.6 Reporter: Henning Noeth Assignee: Henning Noeth The '*' operator should implement: https://getbootstrap.com/docs/4.0/layout/grid/#equal-width Which contain the CSS classes: col, col-sm, col-md, col-lg, col-xl The 'auto' operator should implement: https://getbootstrap.com/docs/4.0/layout/grid/#variable-width-content Which contain the CSS classes: col-auto, col-sm-auto, col-md-auto, col-lg-auto, col-xl-auto -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (TOBAGO-1803) Make Tobago buildable and runnable with Java JDK 9
[ https://issues.apache.org/jira/browse/TOBAGO-1803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Udo Schnurpfeil resolved TOBAGO-1803. - Resolution: Fixed > Make Tobago buildable and runnable with Java JDK 9 > -- > > Key: TOBAGO-1803 > URL: https://issues.apache.org/jira/browse/TOBAGO-1803 > Project: MyFaces Tobago > Issue Type: Task > Components: Build, Core >Reporter: Udo Schnurpfeil >Assignee: Udo Schnurpfeil > Fix For: 4.0.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
