f0ef307d2d
timezone offset was calculated and sent from browser to server, it would be applied on utc time generated from '2013-11-22 5:00' format for example and then sent back to browser which would display it thinking it's UTC time using `moment(utc time)` when it's in fact an UTC time we have offseted with the initial user timezone. This is impossible to automatically test in the current app state. Easiest reproduction is in live browser after setting your timezone to `America/New_York`, when setting a topic timer to later_today, after save, the time under the topic should be off to something roughly equal +1/-1 hour to your timezone offset. |
||
|---|---|---|
| .. | ||
| action-summary.js.es6 | ||
| archetype.js.es6 | ||
| badge-grouping.js.es6 | ||
| badge.js.es6 | ||
| category-list.js.es6 | ||
| category.js.es6 | ||
| composer.js.es6 | ||
| draft.js.es6 | ||
| group-history.js.es6 | ||
| group.js.es6 | ||
| input-validation.js.es6 | ||
| invite.js.es6 | ||
| live-post-counts.es6 | ||
| login-method.js.es6 | ||
| model.js.es6 | ||
| nav-item.js.es6 | ||
| permission-type.js.es6 | ||
| post-action-type.js.es6 | ||
| post-stream.js.es6 | ||
| post.js.es6 | ||
| rest.js.es6 | ||
| result-set.js.es6 | ||
| session.js.es6 | ||
| site.js.es6 | ||
| static-page.js.es6 | ||
| store.js.es6 | ||
| tag-group.js.es6 | ||
| topic-details.js.es6 | ||
| topic-list.js.es6 | ||
| topic-timer.js.es6 | ||
| topic-tracking-state.js.es6 | ||
| topic.js.es6 | ||
| trust-level.js.es6 | ||
| user-action-group.js.es6 | ||
| user-action-stat.js.es6 | ||
| user-action.js.es6 | ||
| user-badge.js.es6 | ||
| user-posts-stream.js.es6 | ||
| user-stream.js.es6 | ||
| user.js.es6 | ||