Re: target-page-based (instead of hyperlink-based) fragment?
Re: target-page-based (instead of hyperlink-based) fragment?
- Subject: Re: target-page-based (instead of hyperlink-based) fragment?
- From: Jesse Tayler via Webobjects-dev <email@hidden>
- Date: Sun, 16 Jan 2022 16:31:18 -0500
Not sure of the details on these requirements but I’d bet your client is seeing
things like twitter feeds or various similar interfaces? I’m pretty sure these
are almost all done using javascript to just store a scroll position on page
exit
> On Jan 16, 2022, at 3:53 PM, OCsite via Webobjects-dev
> <email@hidden> wrote:
>
> Hi there,
>
> my client wants me to ensure that a page, when accessed/refreshed in any way,
> automatically scrolls to a specific place (which depends on previous usage of
> the thing).
>
> Is there some place/hook in WebObjects which would allow me to automatically
> add a fragment (whose value is set up e.g., as
> component.currentFragmentIdentifier) to any URL which goes into that page,
> regardless the URL source?
>
> Adding manually the fragment to all hyperlinks and forms which happen to lead
> to the particular page is conceptually possible, but lots of legwork I could
> do without, if there's another way to do that.
>
> Thanks a lot,
> OC
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden