- 14 2月, 2017 4 次提交
-
-
由 Chinmay Garde 提交于
-
由 Ryan Macnak 提交于
See issue flutter/flutter#8115
-
由 James Robinson 提交于
-
由 Ryan Macnak 提交于
Picks up changes to include inlined frames and line numbers in AOT stack traces.
-
- 11 2月, 2017 4 次提交
-
-
由 Chinmay Garde 提交于
-
由 xster 提交于
-
-
由 Chinmay Garde 提交于
-
- 10 2月, 2017 5 次提交
-
-
由 xster 提交于
-
由 Zachary Anderson 提交于
In a previous change I re-included the observatory assets in the Fuchsia build, but didn't notice this bit here. After this, if Settings::enable_observatory can be set to true somehow, the Observatory will come up in Flutter apps on Fuchsia. Unfortunately, I'm not sure how to do that.
-
由 xster 提交于
* Document the need to sync the engine repo to avoid #8005 * Flit gclient sync and git pull
-
-
由 Hans Muller 提交于
-
- 09 2月, 2017 2 次提交
-
-
由 xster 提交于
-
由 James Robinson 提交于
-
- 08 2月, 2017 5 次提交
-
-
由 Collin Jackson 提交于
-
由 Chris Bracken 提交于
Ensure that the text input keyboard is reloaded if the view keyboardType changes.
-
由 Chinmay Garde 提交于
-
由 Chinmay Garde 提交于
-
-
- 07 2月, 2017 2 次提交
-
-
由 Chris Bracken 提交于
Added: * UIRequiredDeviceCapabilities=[arm64] * MinimumOSVersion=8.0
-
由 Jason Simmons 提交于
-
- 04 2月, 2017 3 次提交
-
-
由 Jason Simmons 提交于
-
-
由 Jason Simmons 提交于
-
- 03 2月, 2017 2 次提交
-
-
由 Chris Bracken 提交于
Provide a default status bar tap handler for FlutterAppDelegate. By default, taps are passed to the key window's rootViewController if it's a FlutterViewController. Apps with custom app delegates can customize this behaviour to send the tap to the FlutterViewController(s) they prefer by overriding touchesBegan:withEvent.
-
由 Jason Simmons 提交于
-
- 02 2月, 2017 5 次提交
-
-
由 Michael Goderbauer 提交于
-
由 Chinmay Garde 提交于
-
由 Chinmay Garde 提交于
-
由 Chinmay Garde 提交于
* [iOS] Ensure FlutterMain is called before interacting with the engine in any way. * Licenses
-
由 Jason Simmons 提交于
-
- 01 2月, 2017 5 次提交
-
-
由 Michael Goderbauer 提交于
-
由 Jason Simmons 提交于
The PlatformView superclass constructor was posting a task to the UI thread that adds the view to the shell's global list. This could result in UI thread operations seeing PlatformView instances that are not fully constructed and do not yet have an engine. This was happening in https://github.com/flutter/flutter/issues/7735
-
由 Chris Bracken 提交于
On iOS, when a tap is detected in the status bar, provide a means to pass that touch event through to one or more FlutterViewControllers to trigger a scroll to top. In iOS apps, scroll to top should occur under the following conditions: 1. There is one and only one UIScrollView visible with scrollsToTop == YES. 2. The status-bar is in standard height mode, not in double-height mode. In double-height mode, the expected behaviour is to trigger a switch to the application associated with the double-height status bar. 3. A tap or a drag gesture occurs that is entirely constrained to the status bar frame. (We currently only handle the tap scenario). Unfortunately, AppDelegates only get touchesBegan events for status bar taps, though get get touchesBegan and touchesEnded events for drags within the status bar frame. As such, we currently synthesise the touchesEnded event for taps.
-
由 Chinmay Garde 提交于
-
由 Michael Goderbauer 提交于
-
- 31 1月, 2017 2 次提交
-
-
由 Chinmay Garde 提交于
-
由 Jason Simmons 提交于
The Dart tests were migrated from the flutter/test/engine suite in the framework repository
-
- 28 1月, 2017 1 次提交
-
-
由 Jason Simmons 提交于
-