Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>To answer your question about documentation of this behavior: It's not Microsoft documentation, but I have a couple of WPF books that both mention this.</p> <p>"<a href="http://rads.stackoverflow.com/amzn/click/0321374479" rel="noreferrer">Essential Windows Presentation Foundation</a>" says: (pp. 160-161)</p> <blockquote> <p>There are two interesting models for hosting navigable content: isolated hosting and integrated hosting.</p> <p>With <strong>isolated hosting</strong> the content is not trusted and is run in a completely isolated (sandboxed) environment. This is how WPF content is hosted when running in the system Web browser as a XAML Browser Application. For navigation to another application or HTML content, this isolated hosting model is supported with a <code>Frame</code> object.</p> <p><strong>Integrated hosting,</strong> in which we want the content to behave as part of our application, is not supported at all in the system. When <code>Frame</code> navigates to content within the application, we get an odd hybrid of isolated and integrated behavior. <code>Frame</code> isolates its content from its style (and its parent's style), but not from the application's style. Events don't bubble from the content in <code>Frame</code>; however, the objects are accessible from the <code>Content</code> property (meaning that they aren't isolated in a security sense).</p> <p>For all these reasons, <code>Frame</code> is most useful when we're working with external content, but it can be carefully used for application content.</p> </blockquote> <p>That's all it has to say -- nothing about property inheritance.</p> <p>"<a href="http://rads.stackoverflow.com/amzn/click/0672328917" rel="noreferrer">Windows Presentation Foundation Unleashed</a> says (p. 95):</p> <blockquote> <p>The <code>Frame</code> control holds arbitrary content, just like all other content controls, but it isolates the content from the rest of the UI. For example, properties that would normally be inherited down the element tree stop when they reach the <code>Frame</code>.</p> </blockquote>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload