- 17 10月, 2020 6 次提交
-
-
由 skia-flutter-autoroll 提交于
-
由 skia-flutter-autoroll 提交于
https://dart.googlesource.com/sdk.git/+log/e655b9a3839e..b58cfe5ab24e 2020-10-16 dart-luci-ci-builder@dart-ci.iam.gserviceaccount.com Version 2.11.0-230.0.dev If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/dart-sdk-flutter-engine Please CC dart-vm-team@google.com,asiva@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md
-
由 skia-flutter-autoroll 提交于
-
由 Chris Bracken 提交于
This removes most of the remaining FLUTTER_NOLINT comments and opts these files back into linter enforcement. I've filed https://github.com/flutter/flutter/issues/68273 to require that all FLUTTER_NOLINT comments be followed by a GitHub issue URL describing the problem to be fixed.
-
由 skia-flutter-autoroll 提交于
-
由 skia-flutter-autoroll 提交于
-
- 16 10月, 2020 22 次提交
-
-
由 Mehmet Fidanboylu 提交于
-
由 skia-flutter-autoroll 提交于
-
由 skia-flutter-autoroll 提交于
-
由 skia-flutter-autoroll 提交于
-
由 Kaushik Iska 提交于
-
由 Kaushik Iska 提交于
Changing it to shared_ptr and migrating the ownership from surface to platform view.
-
由 Chris Bracken 提交于
* Add multi-step IME support to TextInputModel This updates the platform-independent TextInputModel to add support for input method (abbreviated IM or IME) composing regions. In contrast to languages such as English, where keyboard input is managed keystroke-by-keystroke, languages such as Japanese require a multi-step input process wherein the user begins a composing sequence, during which point their keystrokes are captured by a system input method and converted into a text sequence. During composing, the user is able to edit the composing range and manage the conversion from keyboard input to text before eventually committing the text to the underlying text input field. To illustrate this, in Japanese, this sequence might look something like the following: 1. User types 'k'. The character 'k' is added to the composing region. Typically, the text 'k' will be inserted inline into the underlying text field but the composing range will be highlighted in some manner, frequently with a highlight or underline. 2. User types 'a'. The composing range is replaced with the phonetic kana character 'か' (ka). The composing range continues to be highlighted. 3. User types 'k'. The character 'k' is appended to the composing range such that the highlighted text is now 'かk' 4. User types 'u'. The trailing 'k' is replaced with the phonetic kana character 'く' (ku) such that the composing range now reads 'かく' The composing range continues to be highlighted. 5. The user presses the space bar to convert the kana characters to kanji. The composing range is replaced with '書く' (kaku: to write). 6. The user presses the space bar again to show other conversions. The user's configured input method (for example, ibus) pops up a completions menu populated with alternatives such as 各 (kaku: every), 描く (kaku: to draw), 核 (kaku: pit of a fruit, nucleus), 角 (kaku: angle), etc. 7. The user uses the arrow keys to navigate the completions menu and select the alternative to input. As they do, the inline composing region in the text field is updated. It continues to be highlighted or underlined. 8. The user hits enter to commit the composing region. The text is committed to the underlying text field and the visual highlighting is removed. 9. If the user presses another key, a new composing sequence begins. If a selection is present when composing begins, it is preserved until the first keypress of input is received, at which point the selection is deleted. If a composing sequence is aborted before the first keypress, the selection is preserved. Creating a new selection (with the mouse, for example) aborts composing and the composing region is automatically committed. A composing range and selection, both with an extent, are not permitted to co-exist. During composing, keyboard navigation via the arrow keys, or home and end (or equivalent shortcuts) is restricted to the composing range, as are deletions via backspace and the delete key. This patch adds two new private convenience methods, `editing_range` and `text_range`. The former returns the range for which editing is currently active -- the composing range, if composing, otherwise the full range of the text. The latter, returns a range from position 0 (inclusive) to `text_.length()` exclusive. * Move SetComposingLength to TextRange::set_* Adds set_base, set_extent, set_start, set_end methods to TextRange.
-
由 Kaushik Iska 提交于
-
由 skia-flutter-autoroll 提交于
-
由 Chris Bracken 提交于
Adds tests for TextRange::Contains(const TextRange&) where the range being tested spans the base/extent of the testing range. This was originally intended to land in #21854, but it seems I didn't push the additional tests before landing.
-
由 Chris Bracken 提交于
This fixes Windows build on goma. Rolls in buildroot change https://github.com/flutter/buildroot/pull/406 https://github.com/flutter/engine/pull/21884 by stuartmorgan which removes the /FC flag in Windows builds. That flag is incompatible with upstream goma changes. See: https://source.chromium.org/chromium/chromium/src/+/2e6d17c6948b2ca1e4dbd6bf15fcb52d32fa338d
-
由 Jason Simmons 提交于
-
由 Kaushik Iska 提交于
-
由 gaaclarke 提交于
-
由 Harry Terkelsen 提交于
* WIP on Paragraph * WIP skparagraph * Add more Paragraph features in CanvasKit mode * Fix addRoundRect test * Respond to review comments * Remove unused (and potentially harmful) getters from Sk classes
-
由 Adlai Holler 提交于
This name change has to do with SkDeferredDisplayList, which Flutter does not use. As far as Flutter is concerned, this is a no-op.
-
由 Jenn Magder 提交于
-
由 Jenn Magder 提交于
This reverts commit dc848f15.
-
由 stuartmorgan 提交于
The C++ wrapper's plugin registrar can own plugins to provided lifetime management. However, plugins expect the registrar to be valid for the life of the object, including during destruction, so any owned plugins must be explicitly cleared before any registrar-specific destruction happens.
-
由 Jenn Magder 提交于
* Add flag to not publish the observatory port over mDNS * Review edits * Format
-
由 stuartmorgan 提交于
-
由 Chris Bracken 提交于
Replaces selection_base() and selection_extent() with selection() and SetSelection(int, int) with SetSelection(range). This also adds the following convenience methods to TextRange: * reversed() * Contains(size_t position) * Contains(const TextRange& range) as well as operator== for use in unit tests. When Flutter migrates to C++20, we can replace that method with a default declaration.
-
- 15 10月, 2020 12 次提交
-
-
由 skia-flutter-autoroll 提交于
-
由 skia-flutter-autoroll 提交于
-
由 Robert Ancell 提交于
Explicitly make the X connection for EGL. EGL can mistakenly choose the GBM backend when using EGL_DEFAULT_DISPLAY. Fixes https://github.com/flutter/flutter/issues/60429
-
由 Jason Simmons 提交于
-
由 Greg Spencer 提交于
This fixes the lint script to fail when the clang-tidy command itself fails to execute, and print the exception that was raised.
-
由 Kaushik Iska 提交于
-
由 egdaniel 提交于
Previously Skia did not require the clients to pass in the usage flags and Skia would just assumed they contained specific ones depending on how the client wrapped the VkImage. Now Skia allows the client to pass in the specific usage flags used so that Skia knows exactly what type of operations are legal without having to guess/assume what the client did. Also update to set the sample count as well while I'm in here.
-
由 Jason Simmons 提交于
The character offset passed to isGraphemeBreak is relative to the beginning of the string (not relative to the text_start parameter). This caused bad results when searching for grapheme breaks beyond the first line of text (see https://github.com/flutter/flutter/issues/24802). This PR fixes the offset value. It also reverts the workaround applied in https://github.com/flutter/engine/pull/10063, which caused incorrect calculation of boundaries between graphemes within ligatures.
-
由 skia-flutter-autoroll 提交于
-
由 skia-flutter-autoroll 提交于
-
由 skia-flutter-autoroll 提交于
-