We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 40186
    • 28 Posts
    Okay, I looked at the code of the page.

    1. Between the first and second comments, I notice that the second comment style is quip-comment-alt. In the CSS file, the only thing that style connects to is background-color: #f2f2f2; So, I'm going to guess it's not that style that offers the difference.

    2. There is a suspicious-looking div called class="quip-break". I found it once in the CSS file, with the following code attached: .quip-break { clear: left; }. So, I changed that to .quip-break { clear: none; }. No apparent effect.

    3. I cruised into core/components/quip/elements/chunks/quipcomment.chunk.tpl and found the div class="quip-break" and commented that out: <!-- <div class="quip-break"></div> -->. Still no love.

    4. The next thing in the source listing I found was the div class="quip-comment-options". For that, I just cheated and went right to core/components/quip/elements/chunks/quipcomment.chunk.tpl and commented it out as well.

    5. That seemed to do it.

    6. So, I copied the contents of core/components/quip/elements/chunks/quipcomment.chunk.tpl to a new chunk called quipComment

    7. Still appears to be good.

    8. Deleted all my test comments.

    9. Still looks good.

    Oooookay, I think I'm gonna call this happymaking.

    Thank you so much for pointing me to the right chunks! I could not have done this without your help!

    Cheers,

    Edward
    [ed. note: edwardmartiniii last edited this post 14 years, 1 month ago.]
      • 39932
      • 483 Posts
      You're very welcome. Me and Articles had a fight (which comes with Quip). I was determined not to lose. I did not. We still argue, but not nearly as much. Articles is like my teenage son. And Quip was like his best friend... hanging around and doesn't hate me, but can't say that in front of his best friend.
        Website: Extended Dialog Development Blog: on Extended Dialog
        Add-ons: AJAX Revolution, RO.IDEs Editor & Framework (in works) Utilities: Plugin Compatibility List
        Tutorials: Create Cross-Context Resources, Cross-Context AJAX Login, Template-Based Actions, Remove Extensions from URLs

        Failure is just another word for saying you didn't want to try. "It can't be done" means "I don't know how".
        • 44580
        • 189 Posts
        Quote from: fuzzicallogic at Sep 07, 2012, 12:02 PM
        Check this file:

        "core/assets/components/quip/css/web.css"

        Again, don't modify this file. Just copy the selectors to your own CSS and mark them !important and change them

        Hopefully you're still watching this fuzzi...

        I want to make a LARGE number of changes to the CSS, but I don't want to have to re-invent the wheel. So I would like to copy webb.css and point Quip to use the copy instead of the original and then change what I want to change. Is there any way of doing this without hacking original code? It does not seem to be a setting anywhere (IMHO it should be). I don't like using !important.