You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Of course a different template can do it differently. I don't believe the code touches on this (better verify that).
Currently the border is applied to the element itself. This has advantages and makes semantic sense in that it encapsulates the entire element. On the other hand it comes with side-effects, both positive and negative, especially as it relates to the mouse:
It allows you (using only the width of the border, which I set at 1px) to hover and click on the outer element without focusing #input or the buttons.
Mousing from outside the element into a button: #hover(), the outer element handler, fires first. This can cause the image to flicker on idle before displaying the button. I don't know which would fire first without the border on the outer element...
...I have a vague memory of more side-effects.
The border could be on #input instead, as the size is the same (the buttons overlap #input). But I think that would come with its own set of side-effects.
The text was updated successfully, but these errors were encountered:
Of course a different template can do it differently. I don't believe the code touches on this (better verify that).
Currently the border is applied to the element itself. This has advantages and makes semantic sense in that it encapsulates the entire element. On the other hand it comes with side-effects, both positive and negative, especially as it relates to the mouse:
#input
or the buttons.#hover()
, the outer element handler, fires first. This can cause the image to flicker onidle
before displaying the button. I don't know which would fire first without the border on the outer element...The border could be on
#input
instead, as the size is the same (the buttons overlap#input
). But I think that would come with its own set of side-effects.The text was updated successfully, but these errors were encountered: