Native layers are drawn above all LC layers regardless of what layer the object is in. This would go for native buttons and other controls as well. An interesting experiment would be to try a native button over the browser widget.
On desktop you can layer over the browser widget using a second stack that has transparency set appropriately and sits in front of the browser stack. Thanks, Brian On Oct 4, 2018, 5:45 PM -0400, Bob Sneidar via use-livecode <use-livecode@lists.runrev.com>, wrote: > I suspect all they did was take the old browser object and wrap it in a > widget that it can respond to and send messages. The old browser was not on a > layer per se. (Actually, nothing is, it's all smoke and mirrors). It would > write or draw if you will to a rect on the screen, and once it did that, none > of the "underlying" objects were accessible until the browser object was > cleared. > > Bob S > > > > On Oct 4, 2018, at 14:07 , dunbarxx via use-livecode > > <use-livecode@lists.runrev.com> wrote: > > > > The browser object sits atop everything else, or rather it is "drawn" over > > everything else... > > > > Hmmm. > > > > OK,this even though the browser object sits in layer 1, and the overlying > > button sits in layer 2. > > So there is a breakdown in the layer paradigm? > > > > Messages are prevented from being generated if a browser widget rect > > encloses the clickLoc in any way. LC "knows" there is a widget there, eh? > > And reserves that rect against any and all messages. > > > > Hmmm. > > > > Craig > > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode