heather9911 / flies

Automatically exported from code.google.com/p/flies
GNU Lesser General Public License v2.1
0 stars 0 forks source link

Use id-based Tab for new Translation Workspace windows #99

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
Can we launch the translation workspace in a new window or tab. It is
metaphorically a separate entity from the rest of the server, and the
transition between the server and the workspace becomes difficult to
communicate when the user transitions between them in place.

Original issue reported on code.google.com by sitap...@gmail.com on 18 May 2010 at 4:27

GoogleCodeExporter commented 9 years ago
I'm not sure about this.  We used to launch a separate window when opening the 
translation editor.  I don't think a web application should go grabbing extra 
tabs for 
itself without the user's say-so (eg shift-click, middle click).  If we force a 
new 
tab, the user doesn't get a choice.

Original comment by sean.flanigan@gmail.com on 28 May 2010 at 5:45

GoogleCodeExporter commented 9 years ago
My thoughts on this: 

I think the 'Translation Workspace' is very much a new workflow starting, and 
as 
such, it makes sense to open it in a new window/tab. If we were to keep it in 
the 
same window, it should look and act like the rest of the application. It 
doesn't, and 
rightfully shouldn't as it has different requirements in terms of screen real 
estate. 

This behavior is consistent with other similar applications.

Original comment by asgeirf on 28 May 2010 at 6:02

GoogleCodeExporter commented 9 years ago
Has been done on 2 Jun 10.

Original comment by Caius.Chance on 3 Jun 2010 at 1:05

GoogleCodeExporter commented 9 years ago
Hi, the selenium does not support target="_blank" attribute in <a>. thus tests 
with
selenium-RC (which will then be integrated with hudson) break.

I agree with Sean, it's better to let users choose whether he/she want to 
stay/new
tab as background/new tab as a foreground.

But, if the final decision is keeping the "new tab" behaviour, then please use
javascript window.open(URL, name). I can then trace the new tab/window with 
name.

Original comment by dingyichen on 4 Jun 2010 at 4:04

GoogleCodeExporter commented 9 years ago
In addition, if, say, a user launches an ja_JP. Later on, if that user click the
launch translation editor again, using window.open(URL, name) ensures the 
content is
replaced in existing window; while target="_blank" will open yet another 
confusing
window/tab.

Original comment by dingyichen on 4 Jun 2010 at 4:13

GoogleCodeExporter commented 9 years ago

Original comment by asgeirf on 14 Jul 2010 at 5:50

GoogleCodeExporter commented 9 years ago

Original comment by asgeirf on 14 Jul 2010 at 5:59

GoogleCodeExporter commented 9 years ago

Original comment by asgeirf on 15 Jul 2010 at 11:55

GoogleCodeExporter commented 9 years ago

Original comment by asgeirf on 15 Jul 2010 at 11:58

GoogleCodeExporter commented 9 years ago

Original comment by sean.flanigan@gmail.com on 14 Feb 2011 at 5:06