Hello!
Since PM 28.0, I've found some bug: in the "datepicker" component, switching buttons for the previous/next months are "glitching" when onMouseOver() event fires. Here the pics of what am I talking about:
Normal:
On mouse over:
Sorry, that screenshots are in "RU" locale, but it doesn't matter, what language is using.
Glitch in prev/next buttons in the "datepicker" component
Moderator: trava90
Forum rules
This board is for technical/general usage questions and troubleshooting for the Pale Moon browser only. The main focus here is on Pale Moon on Windows. Please direct your questions that are specific for Linux and Mac to the dedicated boards for those operating systems.
Technical issues and questions not related to the Pale Moon browser should be posted in other boards!
Please keep off-topic and general discussion out of this board, thank you!
This board is for technical/general usage questions and troubleshooting for the Pale Moon browser only. The main focus here is on Pale Moon on Windows. Please direct your questions that are specific for Linux and Mac to the dedicated boards for those operating systems.
Technical issues and questions not related to the Pale Moon browser should be posted in other boards!
Please keep off-topic and general discussion out of this board, thank you!
- back0rifize
- Moonbather

- Posts: 51
- Joined: 2016-05-08, 02:26
Re: Glitch in prev/next buttons in the "datepicker" component
I confirm this, see Issue #981 (UXP).
UPD: Until this is fixed in the browser, you can work around it by adding the following lines to chrome.manifest:
UPD: Until this is fixed in the browser, you can work around it by adding the following lines to chrome.manifest:
Code: Select all
override chrome://global/skin/arrow/arrow-lft-hov.gif chrome://global/skin/arrow/arrow-lft.gif os=WINNT
override chrome://global/skin/arrow/arrow-rit-hov.gif chrome://global/skin/arrow/arrow-rit.gif os=WINNT
Here are the add-ons I made in a spare time. That was fun!
- back0rifize
- Moonbather

- Posts: 51
- Joined: 2016-05-08, 02:26
Re: Glitch in prev/next buttons in the "datepicker" component
Thanks a lot! It's not critical to me, but I think I have to use your advice
.
Honestly, I thought that my extension has this bug, but I've looked through my *.css code and didn't see any strings of code, that could be a cause of problem.
Honestly, I thought that my extension has this bug, but I've looked through my *.css code and didn't see any strings of code, that could be a cause of problem.
Re: Glitch in prev/next buttons in the "datepicker" component
I think it may be helpful to share how I investigated this issue, so here it is:
1) Install DOM Inspector
2) Open CalenDate
3) Move the mouse over the prev button and press Ctrl+Shift+RightMouseButton to call DOM Inspector:
4) Switch Object Viewer to CSS Rules:
5) From the button context menu select Set Pseudo-classes:
6) Enable :hover pseudo-class:
7) Now we see that list-style-image has been changed:
8) Try to open chrome://global/skin/arrow/arrow-lft-hov.gif and see it's missing:
9) Open UXP Cross-Reference and search for arrow-lft-hov.gif:
10) Next steps relate to the fix itself
1) Install DOM Inspector
2) Open CalenDate
3) Move the mouse over the prev button and press Ctrl+Shift+RightMouseButton to call DOM Inspector:
4) Switch Object Viewer to CSS Rules:
5) From the button context menu select Set Pseudo-classes:
6) Enable :hover pseudo-class:
7) Now we see that list-style-image has been changed:
8) Try to open chrome://global/skin/arrow/arrow-lft-hov.gif and see it's missing:
9) Open UXP Cross-Reference and search for arrow-lft-hov.gif:
10) Next steps relate to the fix itself
Here are the add-ons I made in a spare time. That was fun!
- back0rifize
- Moonbather

- Posts: 51
- Joined: 2016-05-08, 02:26
Re: Glitch in prev/next buttons in the "datepicker" component
Wow, THAT'S the spirit, sweetheart
!
Honestly, I guessed that this glitch is in the PM (not in my extension), but as for me, it was a little bit lazy to go to the Mozilla Central DXR and find out a needed *.css.
Thanks again!
Honestly, I guessed that this glitch is in the PM (not in my extension), but as for me, it was a little bit lazy to go to the Mozilla Central DXR and find out a needed *.css.
Thanks again!
