The standard format for date input fields is mm/dd/yyyy across different browsers (ex. Chrome, Firefox) so we have set this format as an instructional example. The results will be filtered according to a date range when the given values are submitted. If only 'from' date is submitted, pages that are newer or same as 'from' date will be listed. If only 'to' date is submitted, pages that are older or same as 'to' date will be listed.

In T207442#5292321, @dom_walden wrote:

@HMonroy After checking out your patch, when I click the "Mark as reviewed" button it becomes disabled and there is a little spinner, but nothing happens (in the UI) after this to indicate the action has been successful (which it has).

It stays like this.

@Niharika In the code, there was some previous functionality were if the article was marked as Reviewed the message was sent to the reviewer. I could see this behavior now that I'm always displaying the message box. Just to clarify, when the button says "Mark as Unreviewed" the message is also meant to be sent to the creator?

The following change was also implemented as @MusikAnimal noted when reviewing this patch https://gerrit.wikimedia.org/r/#/c/mediawiki/extensions/PageTriage/+/516563/:

This ticket has the same symptoms as T221783, which has been resolved. That solution should fix this problem as well.

This issue touches on the same logic as T221783. If the user is always allowed to download then there is no reason have this code in there. That block prevents downloads/uploads if the translation is not saved, but like @Samwilson mentioned, the disabled state of the upload button is handled separately.

This error happens intermittently, especially when selecting something from the dropdown and when searching too fast. It sometimes occurs when a user inputs the first letter. Using debounce did not help since the error can happen on any request. In order to stop this error message, we would need to modify the search functionality to try/catch these type of thrown errors by the API. Since the search results are coming from the API as JSONP, they can be challenging to catch. This error message does not affect the user; therefore, it can be safely ignored.

The library Leaflet has map zoom icons set to z-index: 800. By default, the .uls-menu class has z-index 1000, and .oo-ui-dialog has z-index 4. Safari/IE renders the Leaflet zoom icon on top of .uls-menu and .oo-ui-dialog, which is due to how different browsers render the elements according to their position. We are overriding the z-index for .uls-menu and .oo-ui-dialog with higher values to force the elements to display on top of the zoom icon on all browsers. In IE/Safari, the .oo-ui-dialog will not render on top of the Leflet zoom icon with any value less than 1000, and the .uls-menu need a value greater than 1000. We increased the .uls-menu z-index to 1020 to make sure that it renders on top of every element.