Custom Query (18300 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (52 - 54 of 18300)

Ticket Resolution Summary Owner Reporter
#16066 fixed dojox/mobile: adapt to the new full-screen mode of Safari in iOS6 Eric Durocher Adrian Vasiliu
Description

In iOS6, Mobile Safari introduced a full-screen mode available only in landscape orientation. Now, dojox/mobile's views don't behave optimally when this new browser feature is used, with respect to: a) the (optional) mechanism for hiding the address bar and b) the placement of fixed footers.

How to reproduce:

  1. Load for instance dojox/mobile/tests/test_ScrollableView-demo-long.html on iOS6 in portrait orientation (tested on iPhone 4S). This test uses the config option mblAlwaysHideAddressBar: true.

=> So far so good. The address bar is hidden, and the fixed footer is correctly placed at the bottom of the page.

  1. Turn the phone in landscape orientation.

=> So far so good, the address bar is still hidden and the footer is still at the expected bottom position.

  1. Touch the "full screen" button in the lower-right corner of Safari's bottom bar.

=> The address bar is still correctly hidden, the fixed header is still at the correct position on the top of the page (so far so good), but the fixed footer is NOT at the bottom of the page. That is, the additional area revealed by the full-screen mode is not used by the dojox/mobile app. Instead, switching to full-screen only has the effect of translating the view toward the top. Changing the orientation to portrait then landscape again puts the app in the optimal full-screen state.

  1. Touch the "full screen" button again to switch off the full-screen mode.

=> The address bar is now visible (it shouldn't), and the fixed footer is NOT visible (it should be visible). Again, changing the orientation to portrait then landscape again puts the app in the correct state.

The same can be reproduced for instance with test_SwapView-demo.html, where the fixed footer is a PageIndicator. In full-screen mode, the address bar is visible (it shouldn't) and the page indicator is not visible (it should be visible).

If the app doesn't configure the mobile view for hiding the address bar, the behavior is the following:

  • Switching to full-screen has the same effect of translating the view toward the top, thus the address bar is unexpectedly hidden while the fixed footer is no longer on the bottom.
  • However, in this case switching off the full-screen mode puts the app back in the expected state (address bar visible and fixed footer at the bottom).
#16090 fixed dojo/touch: on iOS6, the "touches" property is missing on the synthetic touch.move event bill Adrian Vasiliu
Description

For "touchmove" native events, dojo/touch creates a synthetic touch.move event. Now, the trouble is that, in iOS6, this synthetic event does not have a "touches" property, while it does have it on iOS 4 and 5.

This is the cause of a regression on iOS6 that can be seen in demos/touch/demo.html: you can't rotate the pie chart using the two-finger rotate gesture (while it works fine on iOS 4.3.3, 5.0.1 and 5.1.1).

Reproduced on an iPhone 4S under iOS 6 (6.0), using any recent Dojo version (initial 1.8, 1.8-patch or trunk).

The attached test_bug-synthetic-event-ios6.html is a simple test case which demonstrates the difference of behavior on iOS6 vs. iOS4 or 5 while only relying on dojo/touch (no dependency on dojox/gesture, while demos/touch depends on both). How to reproduce:

  1. Run the test on iOS 4 or 5.
  2. Follow the indication written in the app itself (touch and move over the blue upper area, and check the log written in the white area).

=> You can see in the lower part of the window the log traces for three events: a touch.press, a touch.move, and a synthetic touch.move. For all of them, evt.touches is NOT undefined. So far so good.

  1. Run the same test on an iOS6 device.

=> evt.touches is now undefined for the synthetic touch.move (and only for this event).

#16108 fixed dojo/touch: on iOS6, the synthetic touch.move event misses all event's properties bill Adrian Vasiliu
Description

For "touchmove" native events, dojo/touch creates a synthetic touch.move event. Now, the trouble is that, in iOS6, all the properties of the native touchmove event are missing from the synthetic event, while they are available when running on iOS 4 and 5.

Reproduced on iPhone 4S under iOS 6 (6.0), using any recent Dojo version (initial 1.8, 1.8-patch or trunk).

The attached test_bug-synthetic-event-ios6.html is a simple test case which demonstrates the difference of behavior on iOS6 vs. iOS4 or 5. How to reproduce:

  1. Run the test on iOS 4 or 5.
  2. Follow the indication written in the app itself (touch and move over the blue upper area, and check the log written in the white scrollable area).

=> You can see in the lower part of the window the log traces for three events: a touch.press, a touch.move, and a synthetic touch.move. For all these events, all the properties of the event are NOT undefined. So far so good.

  1. Run the same test on an iOS6 device.

=> All the properties present on the native mousemove event are now undefined for the synthetic touch.move (and only for this event).

This is a follow-up of #16090, which holds only for the "touches" property of the event and is fixed in Dojo 1.8.1.

Note: See TracQuery for help on using queries.