Firefox issue with the look

Same problem for me.
No solution?

I’m having the same problem. Actually, I think it was working in FF but something changed (don’t know what) and caused the one-field-per-line problem. I didn’t notice a new FF version downloading, which would be my first guess. My page has a bunch of html mixed in, so it’s probably not the best example.

Indeed, I just updated Firefox and now it looks good.

Hmm.. I just updated FF from 25.0.1 to 26.0 and it is still rendering the form one-field-per-line. I don’t have time to work on this right now… I’ll have to get back to it later. Just an observation: elektrar’s form is still rendering incorrectly with one field per line.

There seems to be trouble with the way Jazzy Forms imports its stylesheet file. The corresponding embedded style tag is marked as “scoped”. Scoped styles are currently only supported by Firefox, that’s why it behaves differently. Interestingly it only breaks things on certain sites, that’s why I haven’t noticed it before. Anyway, I will probably remove the “scoped” keyword in the next update and that’s it.

I think the problem is in the Jazzy Forms name of css file ( 1.css), it’s starting with a number.
If you copy all css rules from that file in your main css theme file everything should work.

That’s really interesting… I tried grofscala’s suggestion and it fixed most of the problem.

Radio buttons are being rendered with the bullet symbols (from the list formatting).

I have an iframe (discussed in an earlier post) that is in an html element that is being rendered too narrow. The CSS I used to fix that problem works in other browsers but does not work in FF.

But, it’s MUCH better — the elements are together in rows the way they were configured.
Rick.

Thanks for pointing out the workaround of moving the rules into the theme’s stylesheet file, grofscala. That definitely should solve the problem until the problem is fixed. However I don’t think it’s because the file name, “1.css” should be a fully qualified file name, for any browser (tested on FF).

You welcome jazzigor, I don’t think too :-), I just assumed something really fast, I’m glad I helped for the moment. I read ones something about that some browsers have problem to read css file names starting with a number… You will find the real reason, I’m sure. . BTW your plugin is great, I’m not using it, I was just helping to a friend who had had a similar problem with it.

With v1.0 the way the stylesheet is imported should improve the compatibility with Firefox and other browsers. Does it solve the issues you are experimenting?

It’s OK now. Thanks.