←back to thread

A BBC navigation bar component broke depending on the external monitor

(www.joshtumath.uk)
293 points ulrischa | 4 comments | 18 Nov 24 15:28 UTC | HN request time: 0.001s | source
Show context
duxup ◴[18 Nov 24 16:45 UTC] No.42174148[source]▶
Why are screenX and screenY relevant here as far as their code goes?

Where they using those values in their code?

Very interesting article but I'm missing the step where it would impact their code ...

replies(1): >>42174292 #
t43562 ◴[18 Nov 24 16:56 UTC] No.42174292[source]▶
...because when they are 0 one can infer that the event came from a keypress rather than a mouse. They want to know this.
replies(3): >>42174436 #>>42174868 #>>42175013 #
1. hyperhopper ◴[18 Nov 24 18:00 UTC] No.42175013[source]▶
This does not work when the mouse is actually at 0,0
replies(1): >>42175496 #
2. xboxnolifes ◴[18 Nov 24 18:42 UTC] No.42175496[source]▶
An imperfect solution for a situation that will practically never happen and have no noticeable downside.
replies(1): >>42179370 #
3. noworriesnate ◴[19 Nov 24 01:49 UTC] No.42179370[source]▶
It'll screw up UI tests
replies(1): >>42179861 #
4. xboxnolifes ◴[19 Nov 24 03:28 UTC] No.42179861{3}[source]▶
Clearly not, otherwise this bug would have been found much sooner.