title: Kendo UI Web Scheduler: In Monthly view mode, events are collapsed into "three points" bar
body: <p>In Monthly view mode (Kendo UI, Q3 2013 SP1 (version 2013.3.1316)), events are collapsed into "three points" bar, even if there is only one event in that day:</p>
  
  <p><img src="https://i.stack.imgur.com/pgBJR.png" alt="Collapsed events in Monthly view"></p>
  
  <p>The Scheduler widget is defined like the following: </p>
  
  <pre><code>&lt;div id="scheduler" style="height:500px"&gt;&lt;/div&gt;
  
  $("#scheduler").kendoScheduler({
      editable: {
          confirmation: false
      },
      resources: ko.observable([
          {
              field: "displayMode",
              dataSource: [
                      { text: "Regular-Other-Future", value: 111, color: "#93D095" },
                      ...
              ]
          }
      ]),
      add: function (e) {
          e.preventDefault();
          // Custom adding implementation
      },
      edit: function (e) {
          e.preventDefault();
          // Custom editing implementation
      },
      remove: function (e) {
          e.preventDefault();
          // Custom removing implementation
      },
      moveStart: function (e) {
          e.preventDefault(); // Prevent drag-and-drop
      },
      move: function (e) {
          e.preventDefault(); // Prevent drag-and-drop
      },
      moveEnd: function (e) {
          e.preventDefault(); // Prevent drag-and-drop
      },
      views: [{ type: "day", showWorkHours: true }, { type: "week", showWorkHours: true, selected: true }, "month", "agenda"],
      timezone: "Etc/UTC",
      date: new Date(),
      dataSource: self.dataSource // self.dataSource is KO observable, which is assigned later with kendo.data.SchedulerDataSource()
  });
  </code></pre>
  
  <p>The most interesting thing is that some time ago the scheduler looked as the following: </p>
  
  <p><img src="https://i.stack.imgur.com/U0A5y.png" alt="Looked before"></p>
  
  <p>I may be wrong but what we changed was updated to 2013.3.1119. Now we use 2013.3.1316, but the issue is still active. </p>
  
  <p>Thank you very much in advance! </p>