My favorites | Sign in
Project Home Issues
New issue   Search
for
  Advanced search   Search tips   Subscriptions
Issue 2384: Safari Webkit (inApp Browser) unexpected beahviour
2 people starred this issue and may be notified of changes. Back to list
Status:  ExportedToGithub
Owner:  ----
Closed:  Aug 2015


Sign in to add a comment
 
Reported by gergely....@gmail.com, Dec 1, 2014
The following line causes unexpected behaviour in Safari Webkit (inApp) browser:

computeTimeTop: function(time) {
                var slatCoverage = (time - this.minTime) / this.slotDuration;

slatCoverage always results to 0 (it works however correctly in safari browser, chrome, etc - just inapp webview on ios), and hence events are not shown on the agenda. Correcting the line like this solves the problem (the problem seems to occure, when to time objects are substracted):

computeTimeTop: function(time) {
                var slatCoverage = (time.valueOf() - this.minTime.valueOf()) / this.slotDuration.valueOf(); 

Sorry for not giving any test case, but as said, this is an inapp solution.
        
        
Dec 14, 2014
Project Member #1 adamrs...@gmail.com
Really? That's a pretty bad bug in the JS runtime.. doing subtraction or division on non-numbers is supposed to *implicitly* call .valueOf(). At some point I can try to recreate this, but could you give more information on how to rig up an "in-app" webkit setup?
Status: Reproducing
Feb 5, 2015
#2 gergely....@gmail.com
Hi, sorry for the late answer. We have an app with a built in browser. Everything runs fine on ios7 and ios8, but on ios6 the line above fails. Adittionally the following line fails also (function DayishDiff):

ms: a.time() - b.time()

Similarly a.time().valueOf() - b.time().valueOf() solves the issue (in this case the problem was, that updateEvent rendered the event always to midnight).


Feb 9, 2015
Project Member #3 adamrs...@gmail.com
Hmmm ok. I gotta weigh how important this is against other bugs...
Labels: Type-Bug
Aug 21, 2015
Project Member #4 adamrs...@gmail.com
Discussion for this issue has moved to the following URL:
https://github.com/fullcalendar/fullcalendar/issues/2649

This is because Google Code is shutting down. Apologies if you are being pestered with these notifications. This is a one-time event.

Happy coding,
Adam
Status: ExportedToGithub
Sign in to add a comment

Powered by Google Project Hosting