On 06/03/2014 18:07, "Reyna, David" <[email protected]> wrote:
>Hmm, > >And we do not want to apply a search filter since I presume the context >and nearby tasks is important. I think it is, yes. > >My proposal is that we add a test that looks for the anchor when >requested in the URL after the pagination, and refetch the next page(s) >until we find it. This is expensive if it ends up on a later page, Should we try to implement it and see how it performs? >but it is a special request and it is important for the customer >experience to not fail. > > >David > > >----- Original Message ----- >From: Ravi Chintakunta [mailto:[email protected]] >Sent: Thursday, March 06, 2014 07:19 AM >To: BARROS PENA, BELEN; Reyna, David >Cc: '[email protected]' <[email protected]> >Subject: RE: Task Details: link for the task order does not take you to >the respective task > >> > >> >The anchors are included on the task summary page. The issue is it >> only >> >works when the task order is on the first page and I noted this in my >> >commit email. With the pagination, we cannot calculate which page the >> >task appears on. >> >> Is this doable, or not really? >> > >I don't think it is doable. I do not see a way to calculate the page the >task appears on, as the order numbering is not consecutive. > >-Ravi _______________________________________________ toaster mailing list [email protected] https://lists.yoctoproject.org/listinfo/toaster
