My use case is even simpler. Basically I have to redirect user (after a button click) on a mounted page with bootstrap tabs and I want to specify the tab to display with URI fragment. But I found it very hard to implement without a proper support of Uri fragment at page parameters level.
On Sun, 29 Dec 2024, 04:12 Maxim Solodovnik, <solomax...@gmail.com> wrote: > On Sun, 29 Dec 2024 at 00:41, Richard Eckart de Castilho <r...@apache.org> > wrote: > > > > Sounds interesting. > > > > For the moment, I am using the WicketStuff URLFragment. > > we are also using this one :) > works as expected due to we are not using '<a name="" ... ' :) > > > It is a bit quirky though. > > One of the problems with URLFragments is that they may have to change > while on the > > same page, e.g. to track some page state such as a position within a > document or > > such. With URL fragments, the distinction between a page and a "single > page application" > > starts to get quite blurry... likewise, the handling of history when the > fragment is involved. > > > > -- Richard > > > > > On 28. Dec 2024, at 17:28, Andrea Del Bene <an.delb...@gmail.com> > wrote: > > > > > > Hi, > > > > > > lately I had to append a URI fragment to a mounted page. The operation > wasn't so trivial as I expected and I ended up with a workaround involving > a custom page mounter that adds the fragment to the generated URL (inside > method buildUrl). I know this might be an uncommon use case, but wouldn't > be nice if we introduce URI fragment support with PageParameters (i.e > adding a /fragment/ field)? Let me know what do you think about this idea. > > > > > > Andrea. > > > > > -- > Best regards, > Maxim >
