Bug 32377 - Previous/Next month links missing on bahn.de website
Summary: Previous/Next month links missing on bahn.de website
Alias: None
Product: WebKit
Classification: Unclassified
Component: DOM (show other bugs)
Version: 528+ (Nightly build)
Hardware: Mac (Intel) OS X 10.6
: P2 Normal
Assignee: Nobody
URL: http://bahn.de
Keywords: InRadar
Depends on:
Blocks: 4948
  Show dependency treegraph
Reported: 2009-12-10 06:01 PST by Sven-S. Porst
Modified: 2010-11-01 22:09 PDT (History)
2 users (show)

See Also:

Screenshot of bahn.de calendar with green notes indicating the problem (119.48 KB, image/png)
2009-12-10 06:01 PST, Sven-S. Porst
no flags Details
reduced test case (159 bytes, text/html)
2009-12-10 09:47 PST, Alexey Proskuryakov
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Sven-S. Porst 2009-12-10 06:01:28 PST
Created attachment 44609 [details]
Screenshot of bahn.de calendar with green notes indicating the problem

The calendar on bahn.de to pick your travel date lacks its previous month / next month arrows when displayed in WebKit (seen in both the  4.0.4 (6531.21.10, r51939) nightly and Google Chrome and many previous versions). This means you cannot use the calendar provided by the site to do anything outside the current month.  

See the attached screenshot for an illustration.

bahn.de is Germany's railway website. It's used by loads of people (including those from other European countries as bahn.de provides timetables for the whole continent as most of the other countries' railway sites are horrible).
Comment 1 Alexey Proskuryakov 2009-12-10 09:47:02 PST
Created attachment 44623 [details]
reduced test case

This site tries setting innerHTML to "&raquo" instead of "»". This is a mistake, but it's harmless in other browsers, so it should be harmless in WebKit, too.
Comment 2 Deirdre Saoirse Moen 2010-11-01 21:24:09 PDT
Not sure when this was resolved, but it appears to work fine in r70732.

Comment 3 Alexey Proskuryakov 2010-11-01 22:09:07 PDT
Almost certainly fixed by HTML5 tokenizer.