In T410709#11396121, @Bugreporter wrote:First this is not considered resolved since nothing is changed in code; Second, did you close the wrong task?
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Feed Search
Nov 21 2025
Nov 21 2025
D-Kuru added a comment to T410709: Add QuickStatements control functionality to Structured Data on Wikimedia Commons.
D-Kuru closed T410709: Add QuickStatements control functionality to Structured Data on Wikimedia Commons as Resolved.
Aklapper:
[...]
I expect a good number of questions if there is any difference in using any of the buttons, and why the heck there are two of them.
[...]
Following the logic in this ticket, if the list of items gets even longer, there should be a third button in the middle?
Bug restest: already FIXED
See: https://www.wikidata.org/w/index.php?title=Q4115189&diff=2432134808&oldid=2431877434
D-Kuru updated the task description for T410708: Move 'Publish changes' button to a more ergonomic position for Structured Data on Wikimedia Commons.
D-Kuru added a comment to T142082: Add another "Add statement" button on top to ensure consistent position.
In T410708#11395143, @Aklapper wrote:[...]
I expect a good number of questions if there is any difference in using any of the buttons, and why the heck there are two of them.
[...]
Following the logic in this ticket, if the list of items gets even longer, there should be a third button in the middle?The solution is not to add more duplicate buttons.
Maybe the solution is to always display one button no matter where the list has been scrolled to, but that's not what this ticket proposes, thus declining.
D-Kuru added a comment to T410708: Move 'Publish changes' button to a more ergonomic position for Structured Data on Wikimedia Commons.
In T410708#11395143, @Aklapper wrote:The button that already exists at the very bottom of the edit field should also exist at the top of the edit field (see image)
I expect a good number of questions if there is any difference in using any of the buttons, and why the heck there are two of them.
If you think two buttons would confuse people, make it an option where the button appears. The main target for me is that the button does not appear on the other side of the list that get's longer and longer with every item added.
With every item you add, the button moves further and further away from the user thus making it more annoying to save your changes
Following the logic in this ticket, if the list of items gets even longer, there should be a third button in the middle?
Sorry, but the "logic" you read into my request is not represented in the text and (IMO) is not logical at all.
I suggest carefully reading the text again as if you do, the target of it is very clear: "button 'moves away' from the user", "With every item you add, the button moves further and further away", "user can make a change and save it right away exactly where their mouse cursor is", "They don't need to move the mouse cursor to the other side of the edit field or scroll through a long list.", "this would result in less mouse movement and a more ergonomic edit of structured data"
D-Kuru renamed T410708: Move 'Publish changes' button to a more ergonomic position for Structured Data on Wikimedia Commons from Add additional 'Publish changes' button at the top of the edit field for Structured Data on Wikimedia Commons to Move 'Publish changes' button to a more ergonomic position for Structured Data on Wikimedia Commons.
D-Kuru updated the task description for T410708: Move 'Publish changes' button to a more ergonomic position for Structured Data on Wikimedia Commons.
D-Kuru updated the task description for T410709: Add QuickStatements control functionality to Structured Data on Wikimedia Commons.
Feb 12 2020
Feb 12 2020
Jan 22 2020
Jan 22 2020
Nov 25 2019
Nov 25 2019
Note: Wikidata item ".460 Steyr" has been redirected to Q18404479
Nov 23 2019
Nov 23 2019
Content licensed under Creative Commons Attribution-ShareAlike (CC BY-SA) 4.0 unless otherwise noted; code licensed under GNU General Public License (GPL) 2.0 or later and other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL · Credits