| Summary | Date() usage in javascript calendar incompatible with Safari |
| Queue | Kronolith |
| Queue Version | 2.0.3 |
| Type | Bug |
| State | Resolved |
| Priority | 1. Low |
| Owners | |
| Requester | t.zell (at) gmx (dot) de |
| Created | 08/15/2005 (7237 days ago) |
| Due | |
| Updated | 08/15/2005 (7237 days ago) |
| Assigned | |
| Resolved | 08/15/2005 (7237 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
State ⇒ Resolved
State ⇒ Unconfirmed
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ Date() usage in javascript calendar incompatible with Safari
Queue ⇒ Kronolith
New Attachment: goto_inc_patch.diff
month=-1 and expects it to wrap this "out of range" value to month=11
and year-=1.
While most browser in fact to this, Safari interprets this as month=0
and leaves the year as it is. The effect is, that it is not possible
to go backwards one month if the current month is January.
I filed the same bugreport for the open_calendar.js from the Horde
base package.