lynx_view_ios 1.8.1

iOS implementation of the lynx_view plugin (wraps Lynx's native LynxView as a Flutter PlatformView).

1.8.1

• The platform view factory now registers with the WaitUntilTouchesEnded gesture-blocking policy instead of the default Eager. Under Eager, Flutter guarantees a platform view's gesture recognizers only their touchesBegan — the rest of a touch sequence may be cut off mid-stream whenever the framework decides to block — and Lynx recognizes taps with its own native UITapGestureRecognizer, so taps intermittently vanished. With WaitUntilTouchesEnded the recognizers see every sequence whole and blocking applies only to recognition, at the end of the sequence.
• Trade-off: raw touch events of a sequence that a Flutter widget wins still reach the bundle; only gesture recognition is suppressed. bindtap stays safe, but logic a bundle drives off raw touchstart/touchmove/touchend may see touches that belong to Flutter.

1.8.0

• The first template load now waits until Flutter has given the view a real size. A platform view is created before it is placed, so the factory handed us a zero frame and the load ran against a zero viewport. Lynx resolves %, flex and vh while it lays out and does not redo that on its own, so the template stayed collapsed in the top-left — a spinner pinned to the corner, then a blank screen.
• LynxContainerView already forwarded the real bounds to updateViewport as soon as Flutter placed it. That fixes the viewport, not the layout the template had already done against the old one — which is why hosts were resorting to a 1px resize after onLoadSuccess to force a second pass. Now the first pass is the right one, and there is no second.
• Holding the load reuses the machinery that already holds one behind an in-flight load: newest request wins, and a reload() that arrives before the size is queued rather than dropped. The wait is about a frame, against a load that takes far longer.
• Behavior change worth knowing: a LynxView that Flutter never gives a size to never loads its bundle. Parking one in a zero-height box no longer pre-warms it — it rendered nothing either way.

1.7.1

• Call LynxFontFaceManager.shared().register(_:forName:), the names Swift actually imports. 1.7.0 used the raw Objective-C selectors and did not compile.

1.7.0

• Registers the fonts creation param with Lynx before building the LynxView. Each asset is registered with CoreText and then handed to LynxFontFaceManager under the host-chosen family name; Lynx uses that face as-is and only resizes it, which is why one family is one weight.
• Families are registered once per process. CoreText refuses the same graphics font twice, and re-reading a CJK font per view creation is megabytes of needless work.

1.6.0

• Splits Lynx error reporting by LynxError.isFatal: fatal errors keep firing onLoadError, recoverable ones (image fetch failures, runtime warnings) now fire onReceivedError and no longer complete a pending load. Before this, one 404'd <image> killed screens that treat onLoadError as fatal.

1.5.0

• Pulls LynxService/Image so <image> renders remote sources. Lynx delegates all fetch/decode/cache to a registered image service and silently renders nothing without one. Unlike XElement there is no registration code to write: LynxImageService.m self-registers at load via the LynxServiceRegister macro, and the subspec pins its own SDWebImage versions.

1.4.0

• Registers XElement's elements so <input> and friends actually work. The elements ship in one set of subspecs and the code that binds them to tag names ships in another, XElement/Behavior — which depends on XElement/Markdown, which pulls the statically linked ServalMarkdown and LynxTextra. CocoaPods rejects those under use_frameworks!, so the classes linked but stayed unreachable. LynxXElementRegistry now makes the same LynxComponentRegistry calls the upstream macros expand to, looking classes up by name so an excluded subspec registers nothing rather than failing to link.

1.3.0

• Version aligned across the federated packages so they move in lockstep; no functional change in this one.

1.2.1

• Removed the maintainer's Apple DEVELOPMENT_TEAM from the example project.

1.2.0

• Fixed: the native LynxView is now released with Lynx's own clearForDestroy instead of relying on ARC alone, which could leave the engine alive well past dispose().
• Answer trimMemory and queryMemoryUsage on the plugin channel, forwarding to LynxEnv.trimMemory and LynxMemoryUsageQuery.

1.0.1

• Keep Lynx's viewport in sync with the size Flutter gives the platform view. A platform view is created before its size is known, and Lynx was never told the real bounds that arrived afterwards — so templates laid out against a zero viewport, which collapsed flex: 1 to nothing and left %/vh sizes unresolved.

1.0.0

• Initial release: iOS implementation of lynx_view (Lynx SDK 4.0.0 CocoaPods deps, LynxPlatformViewFactory, LynxViewPlugin.registerNativeModule, built-in FlutterBridge module).