Revert "[ermine] disable clipping to unblock roller"

This reverts commit 1a69bda7be8bbe2d48e9a8f4e581bf7fc0b204fd.

Reason for revert: The flutter team reverted the change that required the hard transition. Waiting for the soft transition change to land so we can do this without breaking the UI.

Original change's description:
> [ermine] disable clipping to unblock roller
> 
> The flutter roller is failing because of a breaking
> API change. This code can be uncommented once the
> roll has landed.
> 
> Note: this may cause some visual glitches until the roll happens.
> Change-Id: Iaca1a3658f8fa5f4d3c4a45d1f8cd2d13631b631
> Reviewed-on: https://fuchsia-review.googlesource.com/c/experiences/+/394078
> Reviewed-by: Sanjay Chouksey <sanjayc@google.com>
> Testability-Review: Sanjay Chouksey <sanjayc@google.com>
> Commit-Queue: Chase Latta <chaselatta@google.com>

TBR=jasoncampbell@google.com,chaselatta@google.com,sanjayc@google.com

Change-Id: I2786df0d09c16a706c7351550c1b96345d139b3d
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Reviewed-on: https://fuchsia-review.googlesource.com/c/experiences/+/394157
Reviewed-by: Chase Latta <chaselatta@google.com>
Commit-Queue: Chase Latta <chaselatta@google.com>
1 file changed
tree: ad811fb3287ef348439589c3971eba862b28c454
  1. base_shells/
  2. benchmarks/
  3. bin/
  4. examples/
  5. lib/
  6. session_shells/
  7. settings/
  8. tests/
  9. .gitignore
  10. analysis_options.yaml
  11. AUTHORS
  12. BUILD.gn
  13. CONTRIBUTING.md
  14. LICENSE
  15. OWNERS
  16. PATENTS
  17. README.md
README.md

Fuchsia Experiences Repository

This is a companion repository to Fuchsia and contains code that either implements or supports user facing code for the Fuchsia platform. The code provides a majority of the user interface for the Workstation product as well as a small set of examples, tests, and benchmarks.

Build & Run

This repository is a “source petal” included in the Fuchsia Platform Source Tree (FPST) checkout. Code in this repository must be built with Fuchsia in order to be functional, see (the guide)[https://fuchsia.dev/fuchsia-src/development/source_code] for instructions on getting the source.

Hardware

Hardware support should be considered experimental. However, NUC's and Pixelbooks are known to work best. For details on hardware setup see: (Install Fuchsia on a Device)[https://fuchsia.dev/fuchsia-src/development/hardware/paving]

Building

Once you have functional checkout you can (configure a build)[https://fuchsia.dev/fuchsia-src/development/build/fx#configure-a-build] targeting Workstation:

    fx set workstation.<board> # For options run: `fx list-boards`
    fx build

See Fuchsia's (build and pave instructions)[https://fuchsia.dev/fuchsia-src/development/build/build_and_pave_quickstart] for detailed instructions.

Running

Once built, standard Fuchsia workflows for paving, running code, and testing apply. See: (fx workflows)[https://fuchsia.dev/fuchsia-src/development/build/fx] for detailed instructions.