Opened 7 years ago

Last modified 2 years ago

#16965 assigned defect

[patch][cla] Displacement with TabBar on Android

Reported by: Sebastien Brunot Owned by: Patrick Ruzand
Priority: undecided Milestone: 1.14
Component: DojoX Mobile Version: 1.8.3
Keywords: Cc:
Blocked By: Blocking:

Description

It is thought that the dojox.mobile.TabBar? seems a bit longer than 100% of the screen, made the screen displacement sometimes when users move left or right on the screen ... (see attached screenshot).

It has been reported with Android 2.3.7 and 4.1 on both the stock browser and chrome for Android, and can also be reproduced using the Android 4.1.2 emulator using the stock browser.

Note that with dojo 1.9, a workaround is to set fill to "never" on the TabBar?.

Attachments (1)

screenshot.PNG (77.2 KB) - added by Sebastien Brunot 7 years ago.
screenshot showing the problem

Download all attachments as: .zip

Change History (8)

Changed 7 years ago by Sebastien Brunot

Attachment: screenshot.PNG added

screenshot showing the problem

comment:1 Changed 7 years ago by Sebastien Brunot

Problem reported on the dojo-interest mailing list, using test page dojox/mobile/tests/test_ScrollableView-demo-long.html

comment:2 Changed 7 years ago by Patrick Ruzand

Owner: changed from Eric Durocher to Patrick Ruzand
Status: newassigned

comment:3 Changed 6 years ago by Adrian Vasiliu

The issue goes away by adding

.mblTabBar {
  box-sizing: border-box;
  -moz-box-sizing: border-box;
  -webkit-box-sizing: border-box;
}

(Tested on Galaxy S3 Android 4.3, both Chrome and stock browser.)

That is, it seems to be another symptom of what causes #17764. Both issues go away by this setting of the box model of the TabBar?.

Last edited 6 years ago by Adrian Vasiliu (previous) (diff)

comment:4 Changed 4 years ago by dylan

Milestone: tbd1.11
Summary: Displacement with TabBar on Android[patch][cla] Displacement with TabBar on Android

Looks like a fairly simple CSS addition. Please review and land, or close if you don't intend to land it.

comment:5 Changed 4 years ago by dylan

Milestone: 1.111.12

Ok, after massive triage, ended up with about 80 tickets for 1.11 and 400 or so for 1.12. That's a bit unrealistic, so first I changed all 1.12 to 1.13 (with the plan to move some forward to the new 1.12. Now, I'm moving some of the 1.11 tickets that are less likely to get done this month without help to 1.11. Feel free to help out in January if you want to see this ticket land in 1.11.

comment:6 Changed 3 years ago by dylan

Milestone: 1.121.13

Ticket planning... move current 1.12 tickets out to 1.13 that likely won't get fixed in 1.12.

comment:7 Changed 2 years ago by dylan

Milestone: 1.131.14
Note: See TracTickets for help on using tickets.