year_view: render error in IE8

Scheduler Javascript
#1

Hi.

When using the year_view extension, I have some issues with internet explorer 8.
In FF 3.6.11 it looks as intended but in IE 8 it looks like this:

ie8-yearview.jpg1269×803 253 KB

It seems IE renders the body but shouldn’t do so.

Also: Is it intendet that classes I add to the month_view via

scheduler.templates.month_date_class = function (date, today) {
  if (date.getDay() === 0 || date.getDay() === 6) {return 'weekendMonth';}
  else {return '';}
 };

Is also applied in year_view?

#2

Hello,

  1. Does it work correctly if you comment out all custom css classes which are being assigned?
  2. Also: Is it intendet that classes I add to the month_view via Is also applied in year_view?
    Yes, it certainly works this way for now. If you wish more control over it you can try the following:

scheduler.templates.month_date_class = function (date, today) { if(scheduler.getState().mode == "month") { if (date.getDay() === 0 || date.getDay() === 6) { return 'weekendMonth';} else {return '';} } };
Best regards,
Ilya

#3

  1. Sadly no. Even when I remove the external CSS (with all my custom CSS definitions) it’s still off.

  2. Don’t worry, I was just curious, as the name implies otherwise.

#4
  1. Does our year view sample work correctly for you? (samples\03_extensions\04_year_view.html)
  2. Are you using any plug-in (wordpress, joomla)?
  3. Can you please attach page content (with js code and html markup)?
  4. If you site is available on the Internet - can you give us a link?

Best regards,
Ilya

#5
  1. That example works in IE as intended
  2. No plugins, plain webpage
  3. see attached.
    I had to strip some external script names and such.
    Data is received and written from/to external asp-files. So its not working at all as it is.
    I use some external JS-library (home brew) but functions therein should not effect the view as it is mostly stuff like addEvent and onDomload (cross browser event handling).
    The whole page is heavily work in progress, so please ignore the untidyness :slight_smile:
  4. sorry, not available

I can’t figure out what (apart from CSS, which is not to blame here) could cause the year_view to brake. And in IE only, too…
I hope you have some idea.

Regards,
Gerrit
yearview_broken.zip (5.33 KB)

#6

Ok, i fixed it.

The actual page is in ASP to get some data for select-boxes and such.
In the included asp-library a comment is written to the pages source code stating the sql-call and something else.
The problem in my case arose from the fact that the doctype declaration has to be the first element on a webpage. Obviously IE regards some comment as element as well.
Long story short:

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<!-- Just some comment -->
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
...

yealds the expected result, while

<!-- Just some comment -->
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
...

results in the display error in IE (testet with 6 and 8)

I attached a very simple demonstration file for you to try out.

Please note: i do not regard this a bug in the scheduler
Still, it still works in the other views even with the doctype-quirk, so maybe you can find a solution to make it more robust.

thanks for your help so far.

regards,
Gerrit
yearview-test.zip (844 Bytes)

#7

One more unrelated note:
To identify elements you largely use the name-Attribute.
e.g.


“name” is only valid in form-Elements in some doctypes.
Would be great if you could make the transition to the more plausible (IMHO) id-attribute in some future version.

Regards,
Gerrit

#8

Hello, Gerrit.

Glad your matter is resolved now :slight_smile:

Checked your sample. True, there is always room for improvement yet for now scheduler officially supports only ‘standard’ modes.

Best regards,
Ilya