Open GoogleCodeExporter opened 8 years ago
I am not a huge fan of the word sniping/sniped and I agree that
assassinating/assassinated is too long.
Perhaps closed is fine. Technically, they are closed. The only difference is
that the tab is remembered. How about:
"There are no closed tabs.
"How long to wait before closing an inactive tab"
"How long to remember a closed tab"
Original comment by andyw...@google.com
on 25 Oct 2011 at 10:39
I am worried about using 'closed' because user-closed tabs won't appear there,
which will feel like a bug. I think tab assassin needs some way of
differentiating this class of closedness.
Original comment by est...@chromium.org
on 25 Oct 2011 at 11:03
how about "clear/cleared"? connotes tidiness
Original comment by est...@chromium.org
on 25 Oct 2011 at 11:07
"There are no cleared tabs.
"How long to wait before clearing an inactive tab"
"How long to remember a cleared tab"
I am 75% in move with this?
How about 'removed'?
"No tabs have been removed by the extension."
"How long to wait before the extension removes an inactive tab"
"How long should the extension remember a removed tab"
What do you think about adding the 'the extension' string also?
Original comment by andyw...@google.com
on 26 Oct 2011 at 12:15
"No tabs have been removed by the extension." - Sure. Perhaps the headers could
be simply "Open" and "Recently assassinated" (as I think that "recently" is
another key concept here)
For the options strings, it might be nice to make them sound more active:
"Remove a tab after it has been inactive for: " <input>
"Remember a removed tab for: " <input>
"Do not remove these websites: " <input>
hopefully "the extension" is not necessary here due to the context of being on
the extension's options page.
Original comment by est...@chromium.org
on 26 Oct 2011 at 5:56
make that "Open Tabs" and "Recently Assassinated"
Original comment by est...@chromium.org
on 26 Oct 2011 at 6:01
I like the use of the word 'recently'
I have been thinking of moving away from the word, 'assassinated' as it is not
very user-friendly - or so I have been told. If removed it being used in the
options UI, I think it should be used in the extension UI for consistency.
Original comment by andyw...@google.com
on 26 Oct 2011 at 7:06
Original issue reported on code.google.com by
est...@chromium.org
on 25 Oct 2011 at 8:58