yes, the delay is 150ms after the LINK_DWELL - it doesn't matter if any other state is called in the meantime, code always wait 150ms and fires AJAX request.
I did some testing, and when I move the mouse quickly (like I want to move to a link in the middle of the article) usually I dwell on couple links on the way, the time between LINK_DWELL and ABANDON_START for a link that was on the path of mouse pointer is usually less than 100ms.
Fri, Jun 15
^ revert of last activity made by 238482n375
Thu, Jun 14
@akosiaris - I did couple checks, looks like there are couple errors to investigate and fix (example: trying to 'length' of undefined) and I'll fix those. The majority of those errors come from operations-software-service-checker, the checker has a timelimit=5s and the service from time to time (to be honest it looks like most of the time) doesn't respond in 5 seconds. I'll try to use some easy/lightweight articles so it creates PDF much faster.
Wed, Jun 13
I'll check service logs
@phuedx thx, during one standup I mentioned that the Dashboard is ready, but it contains only an "example" and probably once we get Proton live we will have to revisit the Dashboard and change in the way it meets our expectations. I had no idea how properly organize everything in the way it's readable to non-tech people.
Chromium PDF has some issues with the quality of images, usually, images are printed in low-quality images. Probably Chromium has to fix it first:
I can investigate that topic, but I'm not sure if there is anything we can do right now.
Tue, Jun 12
ABANDON_START has to be lower than FETCH_DELAY_START, otherwise, we trigger AJAX event after every LINK_DWELL event.
- T195991#4259699 - fix by removing max height - @pmiazga to create new ticket, set as low priority - DONE: T197032
- T195991#4261604 - @pmiazga to create spike on how to handle wide tables in PDF, add issues seen in https://en.wikipedia.org/wiki/Mathematics as well - DONE: T197034
- T195991#4259706 - nav boxes not hidden properly - @pmiazga to create a ticket - DONE: T197035
it's difficult to measure 150ms. To verify if this logic works properly, we can increase the timeout from 150ms to like 2s and verify the current fetch dealy start on the local instance.
There should be a 150ms delay before we fire AJAX query https://github.com/wikimedia/mediawiki-extensions-Popups/blob/master/src/actions.js#L16
@ABorbaWMF you can proceed with Phase 3.
Mon, Jun 11
It may be related to the cookie handling, I'll check whats wrong