For input events specifically, Preview events also share event data instances with the equivalent bubbling event.
对于输入事件，预览事件也会特别与对应反升事件共用事件资料执行个体。
Or, if you use a Preview event instance handler to mark the event handled, handlers for the bubbling event will not typically be invoked.
或者，如果您使用预览事件实例处理程序将事件标记为已处理，则通常不会调用冒泡事件的处理程序。
Whether the bubbling or capture phase is used, the default action always happens after all event propagation is finished.
无论使用冒泡阶段还是捕获阶段，默认动作总是在所有的传播完成后执行。
If the event reaches the target element without being handled and the event type allows it, the bubbling phase begins.
如果事件抵达目标元素而没有被处理并且该事件类型允许，则进入冒泡阶段。
The event bubbling technique provides the ability to disconnect the view structure of the widget from the controller code.
事件气泡技巧可用于断开小组件的视图结构与控制器代码之间的连接。
If you need to set up an event observer, should you use the capture or bubbling phase? Here are a few guidelines.
如果需要设置事件观测者，应该使用捕获阶段还是冒泡阶段呢？
The second action in the behavior (stop) is to prevent the event from bubbling up in the browser.
行为中的第二个动作(stop)是为了阻止浏览器中的泡沫事件。
The event travels upwards again and checks if any ancestor element of the target has an event handler for the bubbling phase.
这样就会阻止冒泡阶段事件的继续传播。 阻止捕获阶段的事件传播是不可能的。 有人也许会问为什么。
Also, (not sure about this) I think your script will fire twice because of the event bubbling.
同时，(这个不确定)我觉得你的脚本将火两次因为事件冒泡。
Because of the bubbling routing, the actual element that has capture might be a child element, not necessarily the element where the event handler is actually attached.
由于冒泡路由，因此已执行捕获的实际元素可能是子元素，而不一定是实际附加事件处理程序的元素。
If you use a Preview event class handler to mark the input event handled, the bubbling input event class handler will not be invoked.
如果您使用预览事件类别处理常式将输入事件标记为已处理，便不会叫用反升输入事件类别处理常式。
Because this event USES bubbling routing, the element that has capture might be a child element instead of the element where the event handler is actually attached.
因为这个事件使用反升路由，所以具有捕捉动作的项目可能是子项目，而不是实际附加事件处理常式的项目。
Because this event USES bubbling routing, the element that has capture might be a child element instead of the element where the event handler is actually attached.
因为这个事件使用反升路由，所以具有捕捉动作的项目可能是子项目，而不是实际附加事件处理常式的项目。
应用推荐