aharui commented on issue #963: URL: https://github.com/apache/royale-asjs/issues/963#issuecomment-739448689
I'd recommend stepping through the same code on the JS side. I suspect that SparkContainerView either doesn't add a viewport and just assigns itself as the viewport, or adding yourself somehow doesn't throw an error, and nobody has tried it on SWF. Conceptually, each bead is an encapsulation of some piece of functionality. A View is in charge of the display list, Viewports are in charge of the portion of the display list you can see. Different runtimes/platforms have different feature sets so when you need to do something like clipping or scrolling, the beads in charge of that contain the code to do it, often with conditional compilation for each runtime/platform implementation. Different component sets present different APIs for the consumer. Some might bias a bit towards HTML/JS/CSS, others, like the emulation, are required to present legacy APIs. A Spark Container has legacy APIs for clipping and scrolling. I think there is a functional implementation for JS. Obviously not for SWF. So how to fix it for SWF? Look at the Flash APIs, figure out what to do, and implement it appropriately in the View and Viewport beads, adding SWF-specific support beads if needed. It is ok for the SWF implementation to be completely different from the JS implementation. The JS implementation can take advantage of the HTMLElements having built-in clipping and scrolling. SWF code has to do more work, IIRC. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
