Although, certainly any page that lacks support for iframes is going
to also have significant problems running jQuery.

At this point though, I do agree - a bit too much magic.

--John



On Wed, Dec 9, 2009 at 9:24 AM, Dave Methvin <dave.meth...@gmail.com> wrote:
> This creates a divergence between what a CSS selector means and what a
> jQuery selector means. Think about this code:
>
>  <iframe src="http://google.com";>
>    <p>This browser doesn't support iframes, or has them disabled.</p>
>  </iframe>
>
> This css selector will make the error message bold:
>
> iframe p { font-weight: bold }
>
> With the proposed change, this selector would bold all the p tags in
> the google.com page:
>
> $("iframe p").css("font-weight", "bold");
>
> That's too much magic for me. The iframe contents aren't part of the
> current document, they're in a document unto themselves.
>
> As for how to make selector syntax more symmetrical with the method
> syntax, how about a :contents pseudo?
>
> $("iframe:contents p").addClass("error")  ===  $("iframe").contents
> ().find("p").addClass("error")
>
> --
>
> You received this message because you are subscribed to the Google Groups 
> "jQuery Development" group.
> To post to this group, send email to jquery-...@googlegroups.com.
> To unsubscribe from this group, send email to 
> jquery-dev+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/jquery-dev?hl=en.
>
>
>

--

You received this message because you are subscribed to the Google Groups 
"jQuery Development" group.
To post to this group, send email to jquery-...@googlegroups.com.
To unsubscribe from this group, send email to 
jquery-dev+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/jquery-dev?hl=en.


Reply via email to