1. 16 11月, 2017 5 次提交
    • A
      Enable WebP (#4359) · 5afc1e28
      amirh 提交于
      5afc1e28
    • I
      Allow Flutter apps on Fuchsia to shut down cleanly (#4366) · d917c35e
      Ian McKellar 提交于
      The UIDartState is now always owned by the isolate and always freed in
      the isolate cleanup callback.
      
      In the isolate shutdown callback, if the isolate being shut down is the
      main isolate, the RuntimeController is informed which in turn notifies
      the RuntimeHolder and thus the ApplicationControllerImpl. The
      ApplicationControllerImpl tears down the whole Flutter application.
      
      This fixes Fuchsia bug: MI4-328
      d917c35e
    • Z
      Roll Dart forward (#4363) · 7033e104
      Zachary Anderson 提交于
      7033e104
    • X
      Roll skia (#4364) · 4fcb1925
      xster 提交于
      * roll to 09b8c91b696925c6c6a25c35173f2da27abf0fbe
      
      * update licenses
      4fcb1925
    • B
      Prevent Skia from trying to use stencil buffers (#4362) · e03cab39
      Brian Osman 提交于
      Fixes flutter/flutter#13018
      
      When linear blending was disabled, we started rendering directly to FBO0 again. We can't attach stencil there, and the profile graph code triggers a path that (by default) uses it. This option forces us to use alternate rendering methods.
      
      Note that the graph rendering code is constructing a fairly complex path. It would probably be much faster to render as a simpler series of drawRect calls for each box (which would get batched inside Skia).
      e03cab39
  2. 15 11月, 2017 3 次提交
    • C
      Allow embedders to respond to platform messages from the Dart application. (#4361) · bedba126
      Chinmay Garde 提交于
      This updated the native embedder API in a non-ABI breaking way.
      bedba126
    • A
      roll skia (#4360) · f8c4a02b
      amirh 提交于
      f8c4a02b
    • B
      Disable linear blending, use SkColorSpaceXformCanvas instead (#4355) · 0a7155d4
      Brian Osman 提交于
      This retains gamut correction (adjusting colors for screens with different capabilities), but does all blending and interpolation with sRGB-encoded values. That matches the behavior expected by most users, as well as the behavior of nearly all other systems. It also greatly simplifies the EGL code.
      
      A future Skia change will make this behavior more of a first-class citizen, so some of these implementation details will change again, but the behavior will not. The bulk of this change (elimination of complication from the GL surface code) is permanent - it's just the SkColorSpaceXformCanvas that will be replaced.
      0a7155d4
  3. 14 11月, 2017 3 次提交
  4. 13 11月, 2017 2 次提交
  5. 11 11月, 2017 3 次提交
  6. 10 11月, 2017 8 次提交
  7. 09 11月, 2017 8 次提交
  8. 08 11月, 2017 2 次提交
  9. 07 11月, 2017 2 次提交
  10. 04 11月, 2017 3 次提交
    • C
      Temporaribly disable bottom safe area padding on iOS (#4322) · e059cc02
      Chris Bracken 提交于
      There are two different sets of view insets that applications may want
      to track in order to avoid unwanted interaction with system UI:
      
      1. OS UI that effectively shrinks the Flutter view from a UX point of
         view: e.g., when the keyboard opens, it occludes the bottom of the
         screen and the view should be adjusted such that the bottom, for the
         purposes of scrolling is just above the keyboard.
      2. OS UI that is overlaid over the application, but into which the
         application should draw. e.g., the Home indicator on the iPhone X
         typically appears near the bottom of the screen, overlaid over app
         content. Content should be rendered within this 'safe area' but apps
         should avoid requiring user interaction there. For example, list
         views may want to include some small amount of additional padding to
         ensure the last list item can scroll above this area.
      
      Since Flutter does not currently distinguish between these two cases,
      this patch disables the bottom safe area inset until API is added to
      support these separately.
      e059cc02
    • A
      Followup on post-merge comments for 941ed76b (#4321) · 05b00b1e
      amirh 提交于
      05b00b1e
    • I
  11. 03 11月, 2017 1 次提交