# jere...@gmail.com / 2009-12-18 12:52:08 -0500:
> I read through the thread again last evening, and mulled it over last
> night, and I now agree that there is just too much room for confusion
Thanks for the consideration! IMO (and from my experience) .attr is
needlessly magic and inconsistent (esp. Matt's point regarding readonly
is spot on).
> More importantly though, the functionality is now exposed as a
> quick-setter for newly-created DOM elements, like so (which is,
> ultimately, the result I was trying to achieve with the .attr()
> changes anyway):
> $("<div>", { height: 10, html: "...", id: "test", click: fn })
>
> Note that the above doesn't take a context, thus it only works on the
> current document (which is fine, since we wouldn't want to use the
> method setters on non-HTML documents anyway),
What about (i)frames?
--
Roman Neuhauser
--
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.
