Closed adf-ncgr closed 2 years ago
Yeah, we need to set a policy on new browser windows. My policy has been: if it links a different site, open a new window/tab. The Datastore is a different site, now on a new host: data.legumeinfo.org.
So I propose: use target="_blank" whenever the URL is absolute, not relative, meaning it's a different site.
I'll update all links according to what we decide is the rule. @cann0010 @nathanweeks chime in :)
As for creating a new tab on your own: research showed, at least when I was building websites for a living, that very few people are aware that they can do that, and, rather, simply click links. Given the general lack of tech skills amongst biologists, I'd guess that that is still true for the audience of legumeinfo.org. So I think we should assume that the user will just click a link, and from that decide whether we want it to open in a new tab. (This is a generational thing: I think a lot of schoolchildren these days are taught browser techniques like opening new tabs, but that's not the age group we're hitting.)
I'm OK with 'target="_blank"' for off-site links - though I also share some irritation with this behavior. At the Jekyll-soybase instance, we're trying to minimize the opening of new pages by incorporating some content into iframes. On the main branch (which is about a week behind the scannon branch), you can see this behavior at the tools menu: SequenceServer opens its content in an iframe. In the scannon branch, we've moved most of the tools and the CMap views into iframes - which @nathanweeks facilitated by adding a new full-width iframe layout.
Yer gonna have to work hard to convince me to use iframes on legumeinfo.org. That's a browser window in a browser window which is even worse than a new tab, IMO. For me, a core concept of legumeinfo.org is that it is a portal to other LIS web apps, not a site that pulls LIS web apps into iframes. It's clean and simple. Anyway, what I read was "I'm OK with 'target="_blank"' for off-site links" so I'll count you as a + vote on that policy. :) :)
"I'll count you as a + vote on that policy" - That's fair. As for iframes: I think it depends. Something like SequenceServer is essentially a web app without its own nav system, so it might as well be iframed. Similarly (more or less) for CMap and the genome browsers. The Mines and GCV - I take your point.
Oh, man, I just found this issue, which is on the theme, which I have nothing to do with, jekyll-legumeinfo is now on its own, with its design (there is no _themes directory) many, many changes downstream of the "starter" theme in this repo. Anyway, I checked, and the only use of "_blank" on jekyll-legumeinfo is for sites on different hosts. Note 1: the Datastore is on a different host. Note 2: all tools are on different hosts.
whilst not wishing to make a death-hill out of a mole-hill, I am not sold on the idea that different hosts within the *.legumeinfo.org collective ought to sprout new windows. Do we really want it to feel like the user is going "off-site" if they go to GCV or SequenceServer? Should GCV and SequenceServer also sprout new windows if they provide links back to the legumeinfo.org mothership (or to other tools via linkouts)? I'm iframe-agnostic, but concerned about the potential for user bemusement/irritation (speaking on behalf of the users-already-unable-to-manage-all-the-browser-tabs-they've-sprouted-through-their-own-volition committee). An alternative to the rule you proposed would be that relative URLs and absolute URLs to hosts ending with .legumeinfo.org would not be subject to "off-site treatment"; but maybe this is something for which we need to get some Real User input?
Given that you @adf-ncgr have the most tabs on your browser of any human on Earth, I don't think you're in the best position to argue this point. :) I'm gonna just sit on what I've coded and if there is a community outcry from the LIS group as a whole or actual users, if they exist, I'll update. It's already more of a mountain than a molehill. And this shouldn't be on the theme repo, anyway. We can establish a policy change before launch and implement it.
Closing because this does not belong on the theme repo. Open an issue on jekyll-legumeinfo if you'd like to continue the discussion.
I'm personally not a big fan of not being in control of when a new window is opened; but if there's a compelling reason to have this style of link, then I'd argue we should be consistent about it. Right now, the tools menu on the left hand side seems to do this, while most other links do not (including the tools menu in the navbar). I could see a case for using this style when heading off to twitter or github (as is currently already being done in the navbar).