השבתת ה-endorsement של לינוקס — flutter_inappwebview_linux לא מתקמפל מול WPE 2.36 ושובר את כל בניות הלינוקס#1
Open
palmoni5 wants to merge 4 commits into
Conversation
Batching scroll sends to one platform message per Flutter frame added 0-16ms of variable latency, and in a busy app a delayed or skipped UI frame held trackpad input back and then released it in a burst - scrolling that intermittently ignored the fingers and caught up a moment later. Chromium coalesces a per-event wheel stream by itself (exactly what high-resolution mouse wheels produce natively), so the frame-tied batching only added jitter. Measured with the in-repo smoothness probe (real WebView2, identical synthetic drag): end-to-end latency dropped from 81ms to 56ms and step jitter improved (stdStep 0.66px -> 0.52px, 0% stalled frames) with Chromium smooth scrolling at its default. Also stop the synthetic fling on PointerScrollInertiaCancelEvent, which the engine sends when the user touches the trackpad during inertia. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
1:1 finger-to-page tracking was reported to feel sluggish compared to native precision-touchpad scrolling. Pan deltas (and synthetic fling distances, which pass through the same conversion) are now scaled by a felt gain of 1.5 on top of the measured 120-units-per-100px Chromium wheel calibration, so the page moves 1.5x the finger travel. _kTrackpadGain is the single knob for tuning scroll speed. A synthetic-touch (SendPointerInput PT_TOUCH) alternative was prototyped and measured against a real WebView2: it gives native direct manipulation and Chromium fling, but WebView2 only begins a touch scroll after ~34px of movement per gesture (282ms begin latency, gestures under ~30px scroll nothing). That dead zone kills the small precise scrolls a reading app lives on, so the wheel-injection path stays. Measured after this change (in-repo smoothness probe, real WebView2): page/finger = 1.50 exactly, 0% stalled frames, stdStep 0.44px, 42ms latency, and 8-40px micro-gestures all scroll at full gain. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
… not compile against WPE WebKit 2.36 (Ubuntu 22.04)
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request disables the flutter_inappwebview_linux dependency and its platform endorsement in pubspec.yaml because it requires WPE WebKit >= 2.40, which is incompatible with Ubuntu 22.04's WPE 2.36. There are no review comments, and I have no feedback to provide.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
הבעיה
מאז שמערכת התוספים של Otzaria עברה להשתמש ב-fork הזה (4/4/2026), בניית הלינוקס ב-CI של Otzaria שבורה לחלוטין — אפס ריצות
build_linuxירוקות, והגרסה האחרונה שיצאה ללינוקס היא 0.9.88 (30/3/2026). ריצה נכשלת לדוגמה: https://github.com/Otzaria/otzaria/actions/runs/27395934466סיבת השורש
ה-pubspec של החבילה הראשית מאמץ (endorses) את
flutter_inappwebview_linux: ^0.1.0-beta.1כמימוש ברירת-המחדל ללינוקס. החבילה הזו:wpe-webkit-1.0כ-fallback, אבל קוד ה-C++ משתמש ללא גארדים של גרסה ב-API של WPE WebKit 2.40+: WebKitNetworkSession, WebKitScriptMessageReply, webkit_cookie_manager_get_all_cookies, ו-libsoup3 (GDateTimeבמקוםSoupDate)libwpewebkit-1.0-dev= WPE 2.36 עם libsoup2 → עשרות שגיאות קומפילציה:למה השבתה ולא תיקון
נשקלו החלופות:
השבתת ה-endorsement היא הצעד הנכון כרגע: למשתמשי לינוקס מעולם לא הייתה גרסה עם תוספים (הם תקועים על 0.9.88 שקדמה לפיצ'ר), כך שלא נלקח מהם דבר — ובתמורה הם חוזרים לקבל עדכונים. השינוי הפיך לחלוטין כשהמימוש upstream יבשיל.
השינוי
קובץ אחד —
flutter_inappwebview/pubspec.yaml:linux: default_package: flutter_inappwebview_linuxמ-flutter.plugin.platforms— ה-Flutter tool לא יקמפל יותר את התוסף הנייטיבי בלינוקסflutter_inappwebview_linuxלהערה, עם הסבר קצרהשלכות בצד Otzaria
בלינוקס, קריאות webview יזרקו
MissingPluginExceptionבזמן ריצה. ה-UI של התוספים מגודר היום רק לאנדרואיד/ווינדוס (plugin_tab_page.dart), אז כדאי להוסיף שם מסך "לא נתמך בלינוקס" — יטופל בריפו של Otzaria בנפרד.