Inline citation example wrapped in Firefox

[robertknight]

The inline citation example is wrapped when testing in recent Firefox builds (I'm using FF 19, but I've seen this in earlier FF releases which are not in the FF beta/stable releases) and editing the APA style. Note the line-break between the author and year in the example citations.

Changing the 'display' attribute of the .inline-csl-entry class from 'inline-block' to 'inline' or 'block' fixes the issue.

[SteveRidout]

I can't reproduce with either Chrome, Firefox 16 or 17 (the latest stable release)

I'm curious if you can explain why inline-block should wrap where both inline and block don't. Judging by the screenshot it appears that the div has been made just wide enough to accommodate all the text in both cases, yet it wraps, which seems strange and makes me suspect a Firefox bug.

[robertknight]

As mentioned, I'm using FF Nightlies on Mac. Still happens with my current FF Nightly (FF 20). I'll have to test with the current FF stable builds and get back to you. I don't have an explanation for the difference in behavior between 'inline' and 'inline-block'.

[adam3smith]

I haven't seen this on any browser since, so going to assume this was a fluke with the nightlies back in 2012. Closing.

[zuphilip]

Actually, I see and have seen the line break all the time in Firefox, e.g. now with FF 42.0:

I will try to test/debug it a little...

[adam3smith]

thanks, reopening

[zuphilip]

@adam3smith Actually, you have seen it in the bibliography. The line breaks is really strange. What I see currently is that the div's with the classes inline-csl-entry and bibliography-csl-entry have the wrong width, but this width is a browser CSS style. I can temporarily (in the browser) fix this issue by increase the width or delete the class from the div.

[adam3smith]

you're right. Seeing it locally here on linux, too, now.

[zuphilip]

For firefox we could add

width: -moz-available;

to these two classes base.css. Moreover, this value should be ignored outside Firefox and therefore work as before in Chrome etc.

What do you think? Could this be a solution?