Tapestry 5
  1. Tapestry 5
  2. TAP5-362

Linking to an index page can result in an empty href attribute on a PageLink, which is treated by the browser as staying on the same page

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: 5.0.16
    • Fix Version/s: 5.0.17
    • Component/s: tapestry-core
    • Labels:
      None

      Description

      which is describt here: http://www.nabble.com/-T5--Pagelink-bug-in-Tapestry-5.0.16--td20545079.html#a20545079

      If a layout has a page link like this: <t:pagelink t:page="Index" >Link to start page</t:pagelink>

      will generate a anchor with empty href like this: <a href="">Link to start page </a>

      this works fine under T5.0.15

        Activity

        Hide
        Howard M. Lewis Ship added a comment -

        First I want to verify this.

        Second, does this cause an error? What browser are you using?

        Show
        Howard M. Lewis Ship added a comment - First I want to verify this. Second, does this cause an error? What browser are you using?
        Hide
        Lutz Hühnken added a comment -

        > Does this cause an error?

        Well, it makes it impossible to use a PageLink to link back to the home page (/index) when the context is the root context. Obviously, clicking on a link with an emptry href will cause the browser to stay on the same page.

        > What browser are you using?

        I observed the behaviour with Firefox 3 and Safari on MacOS, but I don't think it is browser specific.

        Show
        Lutz Hühnken added a comment - > Does this cause an error? Well, it makes it impossible to use a PageLink to link back to the home page (/index) when the context is the root context. Obviously, clicking on a link with an emptry href will cause the browser to stay on the same page. > What browser are you using? I observed the behaviour with Firefox 3 and Safari on MacOS, but I don't think it is browser specific.
        Hide
        Stellit Woo added a comment -

        > Does this cause an error?
        There is no "error"(nor any exception) occurred.

        > What browser are you using?
        Webkit(Safari, chromium/chrome), FF3, IE7

        Show
        Stellit Woo added a comment - > Does this cause an error? There is no "error"(nor any exception) occurred. > What browser are you using? Webkit(Safari, chromium/chrome), FF3, IE7
        Hide
        Howard M. Lewis Ship added a comment -

        Verified. There is a workaround, which is to turn of request path optimization.

        Show
        Howard M. Lewis Ship added a comment - Verified. There is a workaround, which is to turn of request path optimization.

          People

          • Assignee:
            Howard M. Lewis Ship
            Reporter:
            Stellit Woo
          • Votes:
            4 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development