line-clamp | WIP - A line clamp '' component | Frontend Framework library

Tailwind's Preflight reset resets lists to be unstyled by default. Without a list-disc or list-decimal utility class, lists will have no bullet or numbers. Using the list-disc/list-decimal sets the list-style-type property, which sets the ::marker pseudo-element to be bullets, numbers, or other things. This is the behavior you see in your first example. The bullet is the browser's default bullet.

When using Tailwind Typography, you should not need to use utility classes within the content, and you may run into unexpected issues with conflicting styles/specificity if you do. In Tailwind Typography, lists are styled by default. However, the typography plugin does not set the ::marker pseudo-element with list-style-type. Instead, it uses the ::before pseudo-element, which allows for more control over the appearance of the bullet.

When using Tailwind Typography and the list-disc utility, these two methods do not conflict, since they do different things, so both are displayed. The darker bullet is likely the ::marker pseudo-element set by list-disc, while the lighter gray bullet is the ::before pseudo-element set by Tailwind Typography. Try using your browser's DevTools to see the pseudo-elements, as well as playing around with what properties are being set and how they affect the appearance.

To avoid this duplicate behavior, simply remove the list-disc class from your list. If you need to customize your Tailwind Typography styles, see the Customization section in the docs. You can also poke around in the source to see how the default styles are set.

You've got an error in your CSS selector for your

You're selecting .list ul when your intention is ul.list

You can just display: inline-block; instead of display: table-cell; in .postInfo.

It's because the website is dynamically rendered. So the javascript first need to run before it shows the product. Therefore you need somewhere to run the javascript (bs can't do that) Have a look at the selinium library.

For displaying the full text from a multiple line snippet of the full text, you can add and remove classes to control the size and the ellipsis status.

I’m not sure there’s a way to put your More / Less button on the same line as the ellipsis, as -webkit-line-clamp ends the text at the end of the line, but you could put the button below the text.

Note: I’m using a button, rather than a link, as a button is better for accessibility (a link goes somewhere, a button does something).

-webkit-line-clamp doesn’t work in IE, so you won’t get the ellipsis, but the text block will still expand.

This solution does require setting the max-height of the text box in the CSS in a couple of places (I’ve used 3.375rem for three lines).

This issue was solved by updating next-pwa 5.2.0, released today, 7th Apr, 2021.

it's because the product_stock variable is undefined when you call it on the script. instead of using javascript code, just add the style directly to the PHP code.

You can do that in php

By looking at the component, you're doing two things upon clicking the button:

• removing the truncate class from the paragraph
• setting truncated property to false.

I would bind the class to the property, using :class="{ truncate: truncated }" and then the only thing in need of testing onclick is that truncated has been set to false (you don't want to test if Vue works).
This removes the need for your showAll to manually remove the class from the paragraph: Vue is data driven => you change the data, Vue manages DOM accordingly.

To make it as clear as possible: you should only test the component's logic and nothing else. You're not testing Vue, JavaScript or the browser. You trust that those work (other people are in charge of writing tests for them). So, in order:

• expect truncated to have the proper value upon mounting (effectively testing isOverflown() provides the expected output in each of the cases you care about)
• when truncated is true trigger a click on the button (no need to expect the button to exist when truncated is true, as you'd be testing if v-if works). After clicking the button, in $nextTick() expect truncated to be set to false.

And here is the list of things you should not test:

• that JavaScript works
• that Vue works (applies :class and :style, applies v-if, etc...)
• that the browser understands and applies -webkit-line-clamp
• that your testing library works
• that showAll has run after clicking the button (you want to be able to rename the method and your test should still pass if clicking the button sets truncated to false).

That's about it.