Browser client iframe (catalog, etc.) loading page
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Medium
|
Unassigned | ||
3.1 |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Evergreen 3.2
In the AngJS browser client, the catalog and various other interfaces are displayed within an iframe. When the iframe is first inserted in the page, the value for the "src" attribute is empty, even when a "src" value has been provided to the egEmbedFrame controller. (Angular applies the "src" attribute after the iframe is added to the DOM).
Because if this, the iframe tries to load a copy of the current page (empty src == "here"), which often results in seeing nested versions of the AngJS app while the page that should be loading is waiting to load.
If the system is slow enough to respond, this nesting can occur by simply navigating to a record detail page (e.g. /eg/staff/
This may be a duplicate of bug #1731272.
See also bug #1731305.
Not only is this confusing, it means the browser is working extra hard to re-render a duplicate AngJS environment.
To prevent the iframe from attempting to load anything other than the desired page at load time, I propose the iframe default to the URL of a simple loading page instead of an empty string. This avoids the unnecessary page load and makes it obvious to users that a page is still loading.
Branch on the way.
Changed in evergreen: | |
importance: | Undecided → Medium |
status: | New → Confirmed |
assignee: | nobody → Galen Charlton (gmc) |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
Patch:
http:// git.evergreen- ils.org/ ?p=working/ Evergreen. git;a=shortlog; h=refs/ heads/user/ berick/ lp1797923- angjs-iframe- loading- page
Going to tag this for back-porting as well, since I consider this to be a bug.