You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Peter Diefenthäler (JIRA)" <ji...@apache.org> on 2011/01/04 12:51:45 UTC

[jira] Created: (WICKET-3306) OrderByBoder MArkup problem

OrderByBoder MArkup problem
---------------------------

                 Key: WICKET-3306
                 URL: https://issues.apache.org/jira/browse/WICKET-3306
             Project: Wicket
          Issue Type: Bug
          Components: wicket-extensions
    Affects Versions: 1.4.15
         Environment: Windows 7, Tomcat 6.x, Eclipse Helios
            Reporter: Peter Diefenthäler
            Priority: Minor


I'm using the OrderByBorder feature and it works well for <th> rows
without stylesheet classes.
Unfortunately it fails if the <th> already has a stylesheet class:

<th class="NameField" wicket:id="orderByName">
        <wicket:message key="nameLabel" />
</th>

Wicket replaces the class="NameField"with the
class="wicket_orderUp" and my field width properties will be lost.
It would be better, if Wicket would add his style class instead of
replacing it (  class="NameField,wicket_orderUp")

public static class CssModifier extends AttributeModifier
This seems to be the problem. 


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (WICKET-3306) OrderByBoder MArkup problem

Posted by "Peter Diefenthäler (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WICKET-3306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Peter Diefenthäler updated WICKET-3306:
---------------------------------------

    Attachment: QuickStart.war

Quick Start application showing the problem.

> OrderByBoder MArkup problem
> ---------------------------
>
>                 Key: WICKET-3306
>                 URL: https://issues.apache.org/jira/browse/WICKET-3306
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket-extensions
>    Affects Versions: 1.4.15
>         Environment: Windows 7, Tomcat 6.x, Eclipse Helios
>            Reporter: Peter Diefenthäler
>            Priority: Minor
>         Attachments: QuickStart.war
>
>
> I'm using the OrderByBorder feature and it works well for <th> rows
> without stylesheet classes.
> Unfortunately it fails if the <th> already has a stylesheet class:
> <th class="NameField" wicket:id="orderByName">
>         <wicket:message key="nameLabel" />
> </th>
> Wicket replaces the class="NameField"with the
> class="wicket_orderUp" and my field width properties will be lost.
> It would be better, if Wicket would add his style class instead of
> replacing it (  class="NameField,wicket_orderUp")
> public static class CssModifier extends AttributeModifier
> This seems to be the problem. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (WICKET-3306) OrderByBoder MArkup problem

Posted by "Hudson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/WICKET-3306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12977356#action_12977356 ] 

Hudson commented on WICKET-3306:
--------------------------------

Integrated in Apache Wicket 1.4.x #367 (See [https://hudson.apache.org/hudson/job/Apache%20Wicket%201.4.x/367/])
    Issue: WICKET-3306


> OrderByBoder MArkup problem
> ---------------------------
>
>                 Key: WICKET-3306
>                 URL: https://issues.apache.org/jira/browse/WICKET-3306
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket-extensions
>    Affects Versions: 1.4.15
>         Environment: Windows 7, Tomcat 6.x, Eclipse Helios
>            Reporter: Peter Diefenthäler
>            Assignee: Igor Vaynberg
>            Priority: Minor
>             Fix For: 1.4.16, 1.5-M4
>
>         Attachments: QuickStart.war
>
>
> I'm using the OrderByBorder feature and it works well for <th> rows
> without stylesheet classes.
> Unfortunately it fails if the <th> already has a stylesheet class:
> <th class="NameField" wicket:id="orderByName">
>         <wicket:message key="nameLabel" />
> </th>
> Wicket replaces the class="NameField"with the
> class="wicket_orderUp" and my field width properties will be lost.
> It would be better, if Wicket would add his style class instead of
> replacing it (  class="NameField,wicket_orderUp")
> public static class CssModifier extends AttributeModifier
> This seems to be the problem. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (WICKET-3306) OrderByBoder MArkup problem

Posted by "Jeremy Thomerson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/WICKET-3306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12977318#action_12977318 ] 

Jeremy Thomerson commented on WICKET-3306:
------------------------------------------

Please attach a real quickstart (with code).  Although outdated, this blog post may help you: http://www.jeremythomerson.com/blog/2008/11/wicket-quickstart-tutorial/

You'll need to do it "the maven way" since that post is so out of date.

> OrderByBoder MArkup problem
> ---------------------------
>
>                 Key: WICKET-3306
>                 URL: https://issues.apache.org/jira/browse/WICKET-3306
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket-extensions
>    Affects Versions: 1.4.15
>         Environment: Windows 7, Tomcat 6.x, Eclipse Helios
>            Reporter: Peter Diefenthäler
>            Priority: Minor
>         Attachments: QuickStart.war
>
>
> I'm using the OrderByBorder feature and it works well for <th> rows
> without stylesheet classes.
> Unfortunately it fails if the <th> already has a stylesheet class:
> <th class="NameField" wicket:id="orderByName">
>         <wicket:message key="nameLabel" />
> </th>
> Wicket replaces the class="NameField"with the
> class="wicket_orderUp" and my field width properties will be lost.
> It would be better, if Wicket would add his style class instead of
> replacing it (  class="NameField,wicket_orderUp")
> public static class CssModifier extends AttributeModifier
> This seems to be the problem. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (WICKET-3306) OrderByBoder MArkup problem

Posted by "Igor Vaynberg (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WICKET-3306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Igor Vaynberg resolved WICKET-3306.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 1.5-M4
                   1.4.16
         Assignee: Igor Vaynberg

> OrderByBoder MArkup problem
> ---------------------------
>
>                 Key: WICKET-3306
>                 URL: https://issues.apache.org/jira/browse/WICKET-3306
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket-extensions
>    Affects Versions: 1.4.15
>         Environment: Windows 7, Tomcat 6.x, Eclipse Helios
>            Reporter: Peter Diefenthäler
>            Assignee: Igor Vaynberg
>            Priority: Minor
>             Fix For: 1.4.16, 1.5-M4
>
>         Attachments: QuickStart.war
>
>
> I'm using the OrderByBorder feature and it works well for <th> rows
> without stylesheet classes.
> Unfortunately it fails if the <th> already has a stylesheet class:
> <th class="NameField" wicket:id="orderByName">
>         <wicket:message key="nameLabel" />
> </th>
> Wicket replaces the class="NameField"with the
> class="wicket_orderUp" and my field width properties will be lost.
> It would be better, if Wicket would add his style class instead of
> replacing it (  class="NameField,wicket_orderUp")
> public static class CssModifier extends AttributeModifier
> This seems to be the problem. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.