Closed slavap closed 5 years ago
eww. wierd. looking at this.
Huh. This looks like you were on the main page of the documentation site. Just tried this, and I don't see it happening.
So, I either fixed it (which I doubt, as I've done nothing).
Or, it's something browser related (maybe). Local date based (maybe).
I dunno. Any help would be cool - OS / Browser / etc.
@jtsage It was not browser or locale related, I had tested it in Chrome and Firefox, and my locale is en_US. I cannot reproduce it on http://dev.jtsage.com/DateBox/ anymore, so probably it's fixed collaterally :-) I will try to update my project from 4.3.1 to the latest version, and let you know if the problem still exists.
Cool. thanks for taking the time.
My fear is that it relates back to a the DST bug, which I kinda knew likely existed, and would crop up in odd ways - although the test dates shouldn't be affected.
At any rate, not much to do until I / we can figure out how to get it to crop up again.
Thanks!
This should be totally fixed in v5. I redid the theme calculations in a sane manner, rather than bolting them on way later.
Yeah, lies, this was an outlier condition that I didn't handle in v5 yet. It's absolutely fixed now., along with an option called "calSelectedOutOfBounds", defaulted to true, which means it will use the selected theme on out of bounds dates.
April to May (bug):
June to May (ok):