This is a pretty conscious decision, because otherwise there would be no way to save a simple snapshot of the current page for pages that have a translator. This might not be a problem for IEEE Xplore, but there are pages like, say, a list of search results in a database, a table of contents for a journal, or a webpage that happens to contain a DOI for some other item, where it's pretty easy to imagine wanting to save the current page and not whatever the translator would yield.

That said, I see why this is confusing. Is there a way that the distinction could be made more clear?

>The user could pick which one of these two is default, and I think the "default default" might be to use the item type. The Create New Item from Current Page icon could also change to indicate which item type it would create (and the drop-down menu would modify that).

That paragraph may be confusing because it was based on a mistaken memory about how buttons with drop-downs on that toolbar worked. I propose something similar to the Notes button which has a two-element dropdown, but the icons should reflect the item type for each option.

At least change the labeling on the button, if we can't make this easier or more intuitive.

"Add Web Page to Library" is clearer about what it's going to do than "Create New Item from Current Page."

WBT

since most of the other buttons on that toolbar are already arrow-drop-downs

That's not an argument for making more of them that way. The current drop-downs are slower than the buttons, and I wish we didn't have them (particularly for notes).

I'm not going to rehash the arguments for the conceptual distance, which I'm pretty sure we've spelled out elsewhere, but for the basic positioning, the obvious justification is that the translator-based save is page-dependent, analogous to the feed auto-discovery icon that Firefox used to display in the address bar (before they removed it due to lack of use). The button in the toolbar isn't page-dependent.

What about "Add a snapshot of this Web Page to Library"?

1) I still don't see the benefit of excluding the "Web Page" item type from the "New Item" drop-down menu. I would just include it, and, like for the other item types, have it create an item without metadata. Say you want to copy web page metadata from an offline source. Currently you either have to create a new item from a different type, and change the type, or create a webpage item from the currently loaded website and change the metadata, or copy an existing web page item and change the metadata. I think those workarounds are worse than possible user confusion between the behavior of "Create New Item from Current Page" and "New Item" > "More" > "Web Page".

2) Another proposal for the label: "Create Web Page Item for Current Page"

Thanks, Rintze. That was it.

1) Well, it's clear from past forum posts that some people are confused as to how to use the "Create New Item from Current Page" button, so the absence of that option has resulted in at least some people figuring out that there's a better way. And the workaround, if you really need to create a web page item manually, is pretty trivial, and certainly takes less time than unnecessarily typing in page details. But there's a valid case to be made that we should privilege proper usage of Zotero rather than putting in an artificial roadblock to prevent improper usage.

2) "Create Web Page Item [from|for] Current Page" is good. I think I prefer "from", though that may be mainly because it's what we're using now.

3) I could see us adding a CWPIfCP button to the browser toolbar by default (and having it be removable via Customize and the Zotero prefs). We have to do something similar in the browser plugins for Standalone anyway. (We also need keyboard shortcuts for both types of saving.) My biggest concern there is that, on Windows and Linux, the default toolbar size would mean that button would be twice the size of the address bar icon, which wouldn't do much to emphasize the superiority of translator-based saving. On the other hand, even if there's less magic involved, snapshots are useful on a wider range of pages.

pull request here:
https://github.com/zotero/zotero/pull/165
you can follow along to see when/if that's going to get accepted.

It was certainly pushed to Transifex — when we push to Transifex, we push everything — but at the time Transifex may not have been properly clearing localized strings when source strings changed.

The right-click option will probably remain in some form, but I'm not sure what. Maybe just a mirror of the toolbar drop-down. In any case, that existing string will go away.

No, that's only to avoid errors in Firefox — it doesn't have an effect on Transifex. When we push to Transifex we only push source (i.e., English) strings.

But anyway, since this change was in 2012, and that message was in 2013, it seems pretty clear this was just a case of that old broken behavior.