Hiroto, reduce the size of double paragraphs

Question

Level 6

13,037 points

Hiroto, reduce the size of double paragraphs

So Jive input froze. Being lazy, I took a picture:

What I want to do is to make these empty paragraphs take up less vertical space. I've looked at the css/html. Apple decide to use !important in min-height. I thought the user css should be last and the last !important should take precedence. The ASC !important wins. Friendly bunch.

Here is a picture of the situation.

The frustrating thing is it works great when I manually insert the element.

I was able to display: none these paragraphs. Risky? I tried to change the attributes on the preceding paragraph, but this didn't have a noticeable effect.

R

Mac mini, OS X Yosemite (10.10.5), Fall 2014; iPhone 4 7.1.2

Posted on Jun 13, 2016 8:18 PM

Reply

Answer 1

Hiroto

Level 5

7,467 points

Jun 14, 2016 1:09 PM in response to rccharles

Hello

To my knowledge of CSS cascading order, the following SHOUD work because user important declaration has higher precedence than author important declaration.

p { min-height: 0px !important; } p[style="min-height: 8pt; height: 8pt; padding: 0px;"] { height: 0.5em !important; }

However this does not work as I expect and I don't know why.

Meanwhile the following appears to work as expected.

.j-thread .jive-content .j-thread-post section p, .j-thread .jive-content .j-thread-post section .jive-rendered-content p, .j-thread .jive-content .j-thread-post section.j-original-message .jive-rendered-content p { min-height: 0px !important; } p[style="min-height: 8pt; height: 8pt; padding: 0px;"] { height: 0.5em !important; }

* This seems to indicate that the specificity of selector plays higher role than origin of rules (user or author) here. However, to my understanding, specificity of selector should matter only for rules which have the same precedence determined by its origin and importance, which is not the case here...

Regards,

H

Reply

Answer 2

rccharles Author

Level 6

13,037 points

Jun 14, 2016 1:47 PM in response to Hiroto

Alleluia, Alleluia. Thanks a bunch. That's going to tighten up the double paragraphs. You got the paragraphs closer together than when I manually inserted css for testing with the inspector.

I'm going to have to re-read the cascading rules again. Got too convoluted for me. I'll have something to follow when reading.

R

Reply

Answer 3

turingtest2

Level 10

278,091 points

Jun 14, 2016 3:30 PM in response to rccharles

I'm been mostly shooting into the dark until I hit something, with a little help from the Google Inspect Element tool. I make no pretensions to a deep understanding, but your question reminded me of this site I ran into a while back:

https://stuffandnonsense.co.uk/archives/css_specificity_wars.html

featuring this wonderful diagram:

tt2

Reply