Bump...
Is this an intended change in 1.3.2? I don't see anything about it in
the release notes...
On Mar 1, 1:59 pm, sliver <sliver2...@gmail.com> wrote:
> Is this a bug in 1.3.2 then?
>
> On Mar 1, 1:16 pm, Frederik Ring <frederik.r...@gmail.com> wrote:
>
> > Looks like this is a 1.3.2 issue I think. Just tried it with 1.2.6 and
> > it returned inline in both cases.
>
> > On Mar 1, 6:31 pm, sliver <sliver2...@gmail.com> wrote:
>
> > > Im not sure if this is intended, but it leads to some unexpected
> > > results:
>
> > > console.log($('<span/>').css('display')); --> 'block'
>
> > > According to W3, span's default display value is inline. Any reason
> > > for the switch?
>
> > > Also, say you have a class definition in a style sheet:
> > > .inline {
> > > display: inline;
>
> > > }
>
> > > console.log($('<div/>').addClass('inline').css('display')); -->
> > > 'block'
>
> > > I would expect it to report 'inline'...
