Selector Polyfill 2: Implement `closestSimple`
Implement closestSimple(node, selector) — a DOM-like polyfill for Element.closest() using only parentNode traversal. Why this is common: closest() is used constantly in event delegation and component boundary checks. Node shape (DOM-like, not real DOM): - tagName: string (case-insensitive) - id?: string - className?: string (space-separated…
What you’ll build / What this tests
This premium javascript coding focuses on Selector Polyfill 2: Implement closestSimple. You’ll apply dom and selectors thinking with intermediate level constraints. The prompt emphasizes Implement closestSimple(node, selector) — a DOM-like polyfill for Element.closest() using only parentNode traversal. Why this is….
Learning goals
- Translate the prompt into a clear javascript API signature and return shape.
- Apply dom, selectors, polyfills techniques to implement selector polyfill 2: implement closestsimple.
- Handle intermediate edge cases without sacrificing readability.
- Reason about time/space complexity and trade-offs in javascript.
Key decisions to discuss
- Define the exact input/output contract before coding.
- Prioritize predictable edge-case handling over micro-optimizations.
Evaluation rubric
- Correctness: covers required behaviors and edge cases.
- Clarity: readable structure and predictable control flow.
- Complexity: avoids unnecessary work for large inputs.
- API discipline: no mutation of inputs; returns expected shape.
- Testability: solution is easy to unit test.
Constraints / Requirements
- Handle empty strings and mixed casing without errors.
- Avoid deep recursion issues on large inputs.
- Do not access the real DOM; use the provided node shape.
- Handle empty or missing inputs without throwing errors.
- Keep runtime close to linear time where possible.
- Prefer a pure function: no side effects beyond the return value.
Mini snippet (usage only)
// Example usage
const node = /* selector polyfill 2: implement `closestsimple` input */;
const selector = /* config */;
const result = closestSimple(node, selector);
console.log(result);
// Edge case check
const empty = node && selector ?? null;
const fallback = closestSimple(node, selector);
console.log(fallback);
// Expected: describe output shape, not the implementation
// (no solution code in preview)Common pitfalls
- Mutating inputs instead of returning a new value.
- Skipping edge cases like empty input, duplicates, or nulls.
- Overlooking time complexity for large inputs.
Related questions
Upgrade to FrontendAtlas Premium to unlock this challenge. Already upgraded? Sign in to continue.