I just realized I do have a Windows 8 laptop where I could test with
Firefox 37.0.2. I saw the same behavior there, with an added problem
where the last page didn't fully load. Screencast at
http://screencast.com/t/yxnvrlhYlr
Refreshing a catalog page is also problematic.
Kathy
On 04/23/2015 05:55 PM, Mike Rylander wrote:
Kathy,
Just to be clear, we're talking about the behaviour in Chrome
specifically, but not Firefox. Is that correct? Your browser controls
were obscured in the screencast, so I just wanted to confirm the
details. Firefox is doing the "right thing" for me.
All,
Here's a direct link to the context-providing wiki page that Kathy
link to through the markmail link below:
http://evergreen-ils.org/dokuwiki/doku.php?id=dev:browser_staff:dev_notes#section20140718
... That explains the background issues in a bit more technical detail.
As a side note, I know that the "double scrollbar" issue has been an
irritation to some. I've removed that for the embedded TPAC, which
was possible because it doesn't use onload handlers to render more
content. The Dojo interfaces will take some more work to handle, but
I think it may be possible to remove their scrollbars as well. That's
for later, though.
Thanks,
--
Mike Rylander
| President
| Equinox Software, Inc. / The Open Source Experts
| phone: 1-877-OPEN-ILS (673-6457)
| email: [email protected] <mailto:[email protected]>
| web: http://www.esilibrary.com
On Thu, Apr 23, 2015 at 3:27 PM, Kathy Lussier <[email protected]
<mailto:[email protected]>> wrote:
Hi all,
After considerable testing of the web client and some follow-up
discussions with Equinox, I would like to revisit a discussion we
had last year regarding catalog integration in the web client -
http://markmail.org/message/zicsno2i7jlshpdb.
I think the use of iframes will be problematic for our users. When
testing, I've found that if I click to view holds for a bib
record, if I then click the browser's back button, I don't return
to the record. Instead, I go back to a different holds view and
then back to the advanced search screen. See the screencast at
https://drive.google.com/open?id=0B74gDMUDwDXqMXhBMlBmQUI3Uk0&authuser=0.
There are navigational elements in the UI to bring users back to
the record or to the search results. However, if there is a
browser back button, people will use it despite those navigational
elements. This is what makes the iframe issue distinct from what
we currently have available in the xul client. There is no
standard back button in the xul client, so people are forced to
use the other navigational elements available in the UI. We don't
have that level of control in the web client.
I am sending this e-mail to see if the collective wisdom of the
developer community may be able to come up with a solution that
will work well for our users. My preference is to not use iframes
at all, but my primary concern is getting the browser navigational
tools to work correctly.
Any thoughts?
Thanks!
Kathy
--
Kathy Lussier
Project Coordinator
Massachusetts Library Network Cooperative
(508) 343-0128 <tel:%28508%29%20343-0128>
[email protected] <mailto:[email protected]>
Twitter: http://www.twitter.com/kmlussier
--
Kathy Lussier
Project Coordinator
Massachusetts Library Network Cooperative
(508) 343-0128
[email protected]
Twitter: http://www.twitter.com/kmlussier
