Odd behaviour when clicking on title hyperlink

Bug #1761276 reported by Christine Burns
62
This bug affects 12 people
Affects Status Importance Assigned to Milestone
Evergreen
Won't Fix
High
Unassigned

Bug Description

EG 3.1rc
This issue only seems to happen in Chrome, not Firefox

In the web client record summary the title field is a link. If you click this link the splash page is displayed and then the record is retrieved. If you use your browser back button you are taken to the splash page, if you press back again you are taken to the original screen.

This behaviour is consistent if you click the title link with the record already open.

I have found this to happen inconsistently if clicking on the title link from other places (Item Status, Items Out etc). Sometimes the record is retrieved quickly without delay - sometimes the splash page appears before the record is retrieved.

This weird redirect does not seem to happen in Firefox.

This issue is hard to capture in screenshot, I have recorded some short videos as examples.

Tags: angular
Revision history for this message
Christine Burns (christine-burns) wrote :
Elaine Hardy (ehardy)
Changed in evergreen:
status: New → Confirmed
Revision history for this message
Elaine Hardy (ehardy) wrote :

And sometimes you get caught on that splash page, from a variety of places, and can't get beyond it without clearing the cached images and files for the browser. In those cases, the url is for the record you are trying to display and not for the home (splash) page -- https://gapines.org/eg/staff/cat/catalog/record/1472631 as opposed to https://gapines.org/eg/staff/ -- but redisplaying won't retrieve the record. Going back and clicking the link again won't either.

Changed in evergreen:
importance: Undecided → High
Revision history for this message
Jeff Davis (jdavis-sitka) wrote :

I can usually reproduce the issue on a 3.1 test server by retrieving record 78 and clicking the title link in record summary. The link URL is /eg/staff/cat/catalog/record/78. When I click it, console debug logs include the following sequence:

egEmbedFrameLoader(): https://dev1.catalogue.libraries.coop/eg/staff/%7B%7Burl%7D%7D (eframe.js:112)
eframe applying xulG handlers: reload (eframe.js:293)
SplashCtrl (VM2657 app.js:153)
egEmbedFrameLoader(): https://dev1.catalogue.libraries.coop/eg/opac//record/78 (eframe.js:112)
eframe applying xulG handlers: reload (eframe.js:293)
record id changed to 78, loading new holdings (app.js:1035)

It looks like that first call to egEmbedFrameLoader is trying to load "/eg/staff/{{url}}" which is not a valid route, so we get bounced to the default route for the base app, i.e. the splash page. Then egEmbedFrameLoader is called again with the correct path for the OPAC iframe. I don't know yet why this is happening (seems like a template is not being parsed correctly?), but I wonder if we can fix the issue by preventing that initial incorrect load.

Revision history for this message
Chris Sharp (chrissharp123) wrote :

I can confirm the problem on Chrome. I can also confirm that the problem does not happen on Firefox.

Revision history for this message
Chris Sharp (chrissharp123) wrote :

(on Evergreen 3.0.2-ish)

Revision history for this message
Christine Burns (christine-burns) wrote :

Evergreen 3.1

I can confirm that the problem does not happen on Firefox.

Revision history for this message
Jeff Davis (jdavis-sitka) wrote :

Ben Holt pointed out that similar-sounding issues have been encountered before by the Angular community. Examples:

https://github.com/angular/angular/issues/23427
https://github.com/angular/angular-cli/issues/7477 (potential mitigation strategies)
https://github.com/angular/angular/issues/16994 (maybe??)

tags: added: webstaffclient
Revision history for this message
Jeff Davis (jdavis-sitka) wrote :

There is discussion of similar-sounding issues in bug 1731272. I tested the fix from that bug's comment #13 but it didn't fix the issue in this bug (I still inconsistently get the splash page during record retrieval).

Revision history for this message
Millissa (millissam) wrote :

We are also experiencing this issue. When we click on the title, it retrieves the record but then goes to a blank search page. If we refresh the page, it loads the correct record. We are on the web client.

tags: added: angular
removed: webstaffclient
Revision history for this message
Michele Morgan (mmorgan) wrote :

I'm unable to reproduce this behavior using Chrome on 3.7.2, 3.8.1 or 3.9.0.

Marking Won't Fix.

Changed in evergreen:
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.