Arbitrary properties for unsupported CSS in Tailwind - Practice Problems & Coding Challenges

Challenge - 5 Problems

📝 Syntax

intermediate

Using arbitrary properties in Tailwind CSS

Which of the following Tailwind CSS classes correctly applies a CSS property scroll-margin-top with a value of 2rem using arbitrary properties?

A scroll-margin-top:2rem

B scroll-margin-top-[2rem]

C [scroll-margin-top:2rem]

D scroll-margin-top(2rem)

💡 Hint

Remember that arbitrary properties in Tailwind use square brackets with the full CSS property and value inside.

Tailwind allows arbitrary CSS properties by wrapping the full property and value inside square brackets, like [property:value]. So [scroll-margin-top:2rem] is correct.

Options A, C, and D are not valid Tailwind arbitrary property syntax.

❓ rendering

intermediate

Visual effect of arbitrary CSS property in Tailwind

Given the following HTML snippet styled with Tailwind CSS, what visual effect will the class [scroll-padding-top:4rem] have when the user scrolls to an anchor link inside the page?

Tailwind

<nav class="fixed top-0 w-full bg-white shadow">
  <a href="#section1" class="block p-4">Section 1</a>
</nav>
<main class="pt-16 [scroll-padding-top:4rem]">
  <section id="section1" class="h-screen bg-gray-100">Content</section>
</main>

A The page will scroll so the top of #section1 is 4rem below the viewport top, avoiding overlap with the fixed nav.

B The page will scroll normally with #section1 at the very top of the viewport, overlapping the fixed nav.

C The page will add 4rem of padding inside #section1, pushing content down visually.

D The page will not scroll at all when clicking the anchor link.

💡 Hint

Scroll padding controls the offset when scrolling to anchors, useful with fixed headers.

The scroll-padding-top property sets the offset from the top of the viewport when scrolling to an anchor. Here, [scroll-padding-top:4rem] ensures the section is visible below the fixed nav bar.

Option A ignores the offset, C changes padding inside the section (not scroll behavior), and D is incorrect.

❓ selector

advanced

Combining arbitrary properties with pseudo-classes in Tailwind

Which Tailwind CSS class correctly applies backdrop-filter: blur(5px) only when the element is hovered?

A hover:backdrop-filter(blur(5px))

B [hover:backdrop-filter:blur(5px)]

C [backdrop-filter:hover:blur(5px)]

D hover:[backdrop-filter:blur(5px)]

💡 Hint

In Tailwind, pseudo-classes come before the arbitrary property in the class name.

The correct syntax is to prefix the arbitrary property with the pseudo-class, like hover:[property:value]. So hover:[backdrop-filter:blur(5px)] applies the blur only on hover.

Other options misuse the brackets or pseudo-class placement.

❓ accessibility

advanced

Accessibility considerations when using arbitrary CSS properties

When using arbitrary CSS properties like [scroll-margin-top:3rem] in Tailwind, which accessibility best practice should you keep in mind?

A Ensure the offset does not hide focused elements or cause keyboard navigation confusion.

B Always add <code>aria-hidden="true"</code> to elements with arbitrary properties.

C Avoid using arbitrary properties because screen readers do not support them.

D Use arbitrary properties only on decorative elements without interactive content.

💡 Hint

Think about how scrolling and focus work for keyboard users.

Using scroll offsets can cause focused elements to be hidden behind fixed headers, confusing keyboard users. So ensure offsets keep focused elements visible.

Options A, B, and C are incorrect or harmful for accessibility.

🧠 Conceptual

expert

Why use arbitrary properties in Tailwind CSS?

Which statement best explains the main advantage of using arbitrary properties like [text-shadow:2px_2px_4px_rgba(0,0,0,0.5)] in Tailwind CSS?

A They enable JavaScript to dynamically change CSS properties without reloading the page.

B They allow applying any CSS property value without needing to extend Tailwind's config or write custom CSS files.

C They replace the need for semantic HTML elements by styling everything inline.

D They automatically optimize CSS for better performance and smaller file size.

💡 Hint

Think about flexibility and avoiding extra setup.

Arbitrary properties let you use any CSS property directly in your class names, so you don't have to add new utilities in Tailwind config or write separate CSS files.

Options B, C, and D describe unrelated or incorrect benefits.