Jason Smith [:jsmith] Reporter
	Description • 12 years ago

Build:

Device - Otoro

Hashes

  <project name="gaia" path="gaia" remote="b2g" revision="ddafa86fc92914306be99c8458362cfc96d44e25"/>
  <project name="releases-mozilla-aurora" path="gecko" remote="mozilla" revision="f950df2007d07a8a6f5c5d5d29383c832249a22e"/>

Steps:

1. Go to December 2012 in the month view from October 2012
2. Switch to the week view

Expected:

November December 2012 shall be shown in the title.

Actual:

December 2012 is shown in the title.

	Sebastian Hengst [:aryx] (needinfo me if it's about an intermittent or backout)
	Comment 1 • 11 years ago

Switching a week back and forth fixes the issue, so it's an initialization issue.

	Adam Rogers (:arog)
	Comment 2 • 11 years ago

I can't recreate this issue, has it been resolved?

If so, we should close this bug.

	Jason Smith [:jsmith] Reporter
	Comment 3 • 11 years ago

Might be - this is an old bug. QA Wanted to confirm this no longer reproduces.

	Andrew Stole [:astole]
	Comment 4 • 11 years ago

QA currently doesn't have an Otoro to test this on.
This issue does not occur on the latest Buri v1.3 build.

Environmental Variables:
Device: Buri v1.3 Mozilla RIL
BuildID: 20140102004001
Gaia: 01e9da49be2cc4bc134eeefc434740d572ec2246
Gecko: 61f553e5db49
Version: 28.0a2
Firmware Version: V1.2_20131115

	Sebastian Hengst [:aryx] (needinfo me if it's about an intermittent or backout)
	Comment 5 • 11 years ago

This is still reproducible with the steps from comment #0 with Geeksphone Keon running Boot2Gecko 1.4.0.0-prerelease 20140103024118.

	Sebastian Hengst [:aryx] (needinfo me if it's about an intermittent or backout)
	Comment 6 • 10 years ago

The behavior depends on the day selected when switching to week view.

Steps to reproduce:
1. Go to month view.
2. Go to April 2014.
3. Select April 1st.
4. Switch to week view.
Actual result: Header is April 2014.
5. Switch back to month view.
6. Select March 31st
7. Select week view.
Actual result: Header is March 2014 April 2014

	Evan Tseng [:evanxd]
	Comment 7 • 10 years ago

Hi Archaeopteryx,
Correct.
It is not an issue.
We should close this bug.

	Sebastian Hengst [:aryx] (needinfo me if it's about an intermittent or backout)
	Comment 8 • 10 years ago

Reopening, this is an issue, but not an important one. It seems to depend on the weekday of the last day of the month, e.g. it's not reproducible with

1. Open September 2014 in month view.
2. Select 29th or 30th.
3. Switch to week view.
Actual and expected result: Header is "Sep 2014 Oct 2014"
If you repeat the steps with Oct 1st or 2nd, only "Oct 2014" will be shown in the header.

For the 'start of the week' view (here Mo-Th), the header is only correct if a day of the old month has been selected.

For the 'end of the week view' I get different results:
May 30th or 31st 2014 (Friday/Saturday): "May 2014"
Oct 31st 2014 (Friday): "Oct 2014 Nov 2014"

	Miller Medeiros [:millermedeiros]
	Comment 9 • 10 years ago

this will be fixed by the 5-day week view

	Miller Medeiros [:millermedeiros]
	Comment 10 • 10 years ago

I'm closing this since it is resolved on master. (by Bug 1023662)

	Elie
	Comment 11 • 10 years ago

This issue still occurs on Flame 2.1
Gaia-Rev        1bdd49770e2cb7a7321e6202c9bf036ab5d8f200
Gecko-Rev       https://hg.mozilla.org/releases/mozilla-b2g34_v2_1/rev/db893274d9a6
Build-ID        20141125001201
Version         34.0
Device-Name     flame
FW-Release      4.4.2

Steps:

1. Go to December 2012 in the month view from October 2012
2. Switch to the week view

Expected:

November December 2012 shall be shown in the title.
Actual:
December 2012 is shown in the title.
log:
happen time:14:52

	Miller Medeiros [:millermedeiros]
	Comment 12 • 9 years ago

Elie, this got fixed many months ago and we didn't change this logic in the past 10 months.. the header is based on the dates that are currently displayed on the week view, when you move to December 2012 (starting from October) it will select December 1st 2012 and week view will display Dec 1st until Dec 5th. So the header is really displaying the correct value for your test case.