Essential CSS
JavaScript Roadmap
Learn JavaScript
Mastering Web Typography
Practical Astro
Understanding Async JS
Unorthodox Tailwind
API Masterclass
Build and Deploy
The Beginner Freelancer
Real World Node
Profile Billing Logout
Learn JavaScript
Lesson Plan
  1. JavaScript and its ecosystem
    1. Welcome to Learn JavaScript!
    2. What is JavaScript used for?
    3. The JavaScript ecosystem
    4. Varying versions of JavaScript
  2. JS Basics
    1. Linking your JavaScript file
    2. Preparing your text editor
    3. The Console
    4. Comments
    5. On semicolons
    6. Strings, numbers and booleans
    7. Understanding Variables
    8. Understanding Functions
    9. The Flow of a Function
    10. Arrow functions
    11. Intro to objects
    12. If/else statements
    13. Comparing Objects
    14. The NOT operator
    15. Null and Undefined
    16. The BOM and the DOM
    17. Selecting an Element
    18. Changing Classes
    19. Listening to events
    20. Callbacks
  3. Building simple components
    1. How to think like a developer
    2. Starter files and Source codes
    3. Do this for every component
    4. đź›  Off-canvas menu: Building an off-canvas menu
    5. đź›  Modal: Building a Modal
    6. Lessons from the building process
    7. Debugging errors
    8. How to use a linter
  4. Arrays and loops
    1. Introduction to Arrays
    2. Array methods
    3. For loops
    4. The forEach loop
    5. Selecting multiple elements
    6. Nodes vs Elements
    7. đź›  Accordion: Building an accordion
  5. Dom basics
    1. Id, classes, attributes, and tags
    2. Changing CSS with JavaScript
    3. Getting CSS with JavaScript
    4. Changing Attributes
    5. Finding an element's size and position
    6. DOM Traversals
    7. đź›  Tabby: Building Tabby (A Tabbed component)
    8. đź›  Carousel: HTML and CSS
    9. đź›  Carousel: Switching slides with JavaScript
    10. đź›  Carousel: Working the dots
    11. đź›  Carousel: Positioning slides with JavaScript
  6. Events deep dive
    1. The listening element
    2. Default Behaviors
    3. Event propagation
    4. Event delegation
    5. Removing Event Listeners
    6. đź›  Modal: Closing the modal
    7. đź›  Accordion: Event delegation
    8. đź›  Tabby: Event delegation
    9. đź›  Carousel: Event delegation
  7. Transitions and Animations
    1. CSS Transitions
    2. CSS Animations
    3. Silky-smooth animations
    4. Integrating CSS transitions and animations with JavaScript
    5. Animating with JavaScript
    6. GreenSock Animation API (GSAP)
    7. đź›  Off-canvas menu: Animations
    8. đź›  Modal: Animating the modal
    9. đź›  Modal: Animating the pointing hand
    10. đź›  Modal: Animating the waving hand
    11. đź›  Modal: Wave hand animation with JavaScript (using GSAP)
    12. đź›  Accordion: Animations
    13. đź›  Carousel: Animations
  8. Useful JS features
    1. Ternary operators
    2. AND and OR operators
    3. Early returns
    4. Template Literals
    5. Destructuring
    6. Default parameters
    7. Enhanced Object Literals
    8. Rest and Spread
    9. Useful array methods
    10. Looping through objects
    11. Returning objects with implicit return
    12. đź›  Accordion: Using useful JavaScript features
    13. đź›  Tabby: Using useful JavaScript features
    14. đź›  Carousel: Useful JavaScript features
  9. JS Best practices
    1. Write declarative code
    2. Functions with a purpose
    3. Manage scope
    4. Reduce state changes
    5. Don't reassign
    6. Don't mutate
    7. Preventing Objects from mutating
    8. Preventing Arrays from mutating
    9. Write pure functions
    10. đź›  Accordion: Refactor
    11. đź›  Carousel: First refactor
    12. đź›  Carousel: Refactoring the dots part
    13. đź›  Carousel: Previous and next buttons
    14. đź›  Carousel: Second refactor
  10. Manipulating text and content
    1. Changing Text and HTML
    2. Creating HTML Elements
    3. Adding multiple elements to the DOM
    4. Removing Elements from the DOM
    5. đź›  Carousel: Creating dots with JavaScript
    6. 🛠️ Calculator: HTML and CSS
    7. 🛠️ Calculator: Happy Path
    8. 🛠️ Calculator: Testing the Happy Path
    9. 🛠️ Calculator: Easy Edge Cases
    10. 🛠️ Calculator: Difficult Edge Cases
    11. 🛠️ Calculator: Refactoring
    12. The switch statement
    13. 🛠️ Calculator: Refactoring (Part 2)
    14. 🛠️ Popover: Making one popover
    15. 🛠️ Popover: Making four popovers
    16. 🛠️ Popover: Making popovers with JavaScript
  11. Handling Forms
    1. Intro to forms
    2. Selecting form fields with JavaScript
    3. Form fields and their events
    4. Sanitize your output
    5. Generating unique IDs
    6. 🛠️ Popover: Dynamic ID
    7. 🛠️ Todolist: The HTML and CSS
    8. 🛠️ Todolist: Creating tasks with JavaScript
    9. 🛠️ Todolist: Deleting tasks with JavaScript
    10. 🛠️ Typeahead: The HTML and CSS
    11. 🛠️ Typeahead: Displaying predictions
    12. 🛠️ Typeahead: Selecting a prediction
    13. 🛠️ Typeahead: Bolding search terms
  12. Handling Dates
    1. The Date object
    2. Getting a formatted date
    3. Getting the time
    4. Local time and UTC Time
    5. Setting a specific date
    6. Setting a date with Date methods
    7. Adding (or subtracting) date and time
    8. Comparing Dates and times
    9. 🛠️ Datepicker: HTML and CSS
    10. 🛠️ Datepicker: Building the calendar
    11. 🛠️ Datepicker: Building the datepicker with JavaScript
    12. 🛠️ Datepicker: Previous and Next buttons
    13. 🛠️ Datepicker: Selecting a date
    14. 🛠️ Datepicker: Positioning the datepicker
    15. 🛠️ Datepicker: Showing and hiding
    16. Formatting a date with toLocaleString
    17. setTimeout
    18. setInterval
    19. 🛠️ Countdown timer: HTML and CSS
    20. 🛠️ Countdown timer: JavaScript
    21. 🛠️ Countdown timer: Counting Months
    22. 🛠️ Countdown timer: Daylight Saving Time
    23. 🛠️ Countdown timer: Counting Years
  13. Async JS
    1. Introduction to Ajax
    2. Understanding JSON
    3. The Fetch API
    4. Possible data types
    5. JavaScript Promises
    6. Requests and responses
    7. Sending a POST request
    8. Authentication
    9. Handling errors
    10. Viewing response headers
    11. CORS and JSONP
    12. XHR vs Fetch
    13. Using an Ajax library
    14. Reading API documentation
    15. Understanding curl
    16. 🛠️ Todolist: The Todolist API
    17. 🛠️ Todolist: Fetching tasks
    18. 🛠️ Todolist: Creating tasks
    19. 🛠️ Todolist: Editing tasks
    20. 🛠️ Todolist: Deleting tasks
    21. 🛠️ Todolist: Creating tasks with Optimistic UI
    22. 🛠️ Todolist: Handling Optimistic UI errors
    23. 🛠️ Todolist: Editing tasks with Optimistic UI
    24. 🛠️ Todolist: Deleting tasks with Optimistic UI
    25. 🛠️ Todolist: Refactor
    26. 🛠️ Typeahead: How to add Ajax
    27. 🛠️ Typeahead: Adding Ajax
    28. 🛠️ Typeahead: Handling errors
    29. 🛠️ Google Maps Clone: Creating your first Google Map
    30. 🛠️ Google Maps Clone: Fetching JSONP via JavaScript
    31. 🛠️ Google Maps Clone: Drawing directions
    32. 🛠️ Google Maps Clone: Driving directions
    33. 🛠️ Google Maps Clone: Handling errors
    34. 🛠️ Google Maps Clone: Adding stopovers
    35. 🛠️ Google Maps Clone: Refactor
  14. Advanced Async JS
    1. Requesting many resources at once
    2. Asynchronous functions
    3. Handling multiple awaits
    4. Asynchronous loops
    5. 🛠️ Dota Heroes: Listing heroes
    6. 🛠️ Dota Heroes: Filtering heroes (Part 1)
    7. 🛠️ Dota Heroes: Filtering heroes (Part 2)
    8. 🛠️ Dota Heroes: Refactoring
    9. 🛠️ Dota Heroes: Hero Page
    10. 🛠️ Dota Heroes: Making the hero page robust
    11. 🛠️ Dota Heroes: Heroes page refactor
  15. Handling Keyboard Events
    1. Keyboard users
    2. Handling commonly used keys
    3. Keyboard events
    4. Understanding Tabindex
    5. Detecting the focused element
    6. Directing focus
    7. Preventing people from tabbing into elements
    8. How to choose keyboard shortcuts
    9. Creating single-key shortcuts
    10. 🛠️ Off-canvas: Adding keyboard interaction
    11. 🛠️ Modal: Adding keyboard interaction
    12. 🛠️ Accordion: Adding keyboard interaction
    13. 🛠️ Tabby: Adding keyboard interaction
    14. 🛠️ Tabby: Refactoring
    15. 🛠️ Carousel: Adding keyboard interaction
    16. 🛠️ Carousel: Displaying help text
    17. 🛠️ Calculator: Adding keyboard interaction
    18. 🛠️ Popover: Keyboard
    19. 🛠️ Popover: Refactor
    20. Keyboard shortcuts with Command and Control modifiers
    21. 🛠️ Todolist: Keyboard
    22. 🛠️ Typeahead: Keyboard
    23. 🛠️ Typeahead: Selecting a prediction with the keyboard
    24. 🛠️ Google Maps Clone: Keyboard
    25. 🛠️ Dota Heroes: Keyboard
    26. 🛠️ Datepicker: Tabbing in and out
    27. 🛠️ Datepicker: Keyboard shortcuts
  16. Screen reader accessibility
    1. What is accessibility?
    2. How to use a screen reader
    3. Using NVDA
    4. Using Voiceover
    5. Aria roles
    6. Landmark roles
    7. Document structure roles
    8. Live region roles
    9. Widget roles
    10. Window and Abstract roles
    11. Accessible names and descriptions
    12. Hiding content
    13. ARIA properties and ARIA states
    14. ARIA for expandable widgets
    15. 🛠️ Off-canvas: Accessibility
    16. ARIA for modal dialogs
    17. 🛠️ Modal: Screen reader accessibility
    18. 🛠️ Accordion: Screen reader accessibility
    19. ARIA for Tabbed components
    20. 🛠️ Tabby: Screen reader accessibility
    21. 🛠️ Tabby: Refactor
    22. 🛠️ Carousel: Screen reader accessibility
    23. Roles that trigger Forms and Application modes
    24. What's next for accessibility?
  17. Handling Scroll
    1. The Scroll event
    2. 🛠️ Auto-hiding Sticky-nav: HTML and CSS
    3. 🛠️ Auto-hiding Sticky-nav: JavaScript
    4. 🛠️ Auto-hiding Sticky-nav: Natural reveal
    5. Intersection Observer API
    6. Intersection Observer Options
    7. 🛠️ Slide & Reveal
    8. 🛠️ Slide & Reveal: Always fade-in when you scroll down
    9. 🛠️ Slide & Reveal: Fine-tuning the animation
    10. 🛠️ Infinite Scroll: Anatomy
    11. 🛠️ Infinite Scroll: Infinite load
    12. 🛠️ Infinite Scroll: Refactor
    13. 🛠️ Infinite Scroll: Implementing the Infinite Scroll
  18. Mouse, Touch, and Pointer events
    1. Mouse Events
    2. 🛠️ Spinning Pacman: HTML and CSS
    3. 🛠️ Spinning Pacman: JavaScript
    4. Touch events
    5. Pointer events
    6. Touch-action
    7. 🛠️ Spinning Pacman: Supporting Touch
    8. Cloning elements
    9. 🛠️ DragDrop: HTML and CSS
    10. 🛠️ DragDrop: JavaScript
    11. 🛠️ DragDrop: Creating a drop preview
    12. 🛠️ DragDrop: Sortable drop preview
    13. 🛠️ DragDrop: Robustness
    14. 🛠️ DragDrop: Refactor
  19. Object Oriented Programming
    1. Before we begin
    2. What is Object Oriented Programming?
    3. Four Flavours of Object Oriented Programming
    4. Inheritance
    5. This in JavaScript
    6. Call, bind, apply
    7. Creating Derivative Objects
    8. Composition vs Inheritance
    9. Polymorphism
    10. Encapsulation
    11. Closures
    12. Encapsulation in Object Oriented Programming
    13. Getters and Setters
    14. What OOP flavour to use
    15. When to use Object Oriented Programming
  20. Writing reusable code
    1. Creating reusable code by writing libraries
    2. Two Types of libraries
    3. Including libraries with Script tags
    4. Including libraries with ES6 Modules
    5. Dynamic imports
    6. 🛠️ Off Canvas: Building a Library
    7. 🛠️ Modal: Library setup
    8. 🛠️ Modal: Opening the Modal
    9. 🛠️ Modal: Closing the modal
    10. 🛠️ Modal: Inheritance and Polymorphism
    11. 🛠️ Modal: Resolving differences between subclasses
    12. 🛠️ Modal: Exposing properties and methods
    13. 🛠️ Accordion: Building a library
    14. 🛠️ Tabby: Building a library
    15. 🛠️ Carousel: Building a library
    16. 🛠️ Calculator: Library
    17. 🛠️ Calculator: Fixing the Clear Key
    18. 🛠️ Calculator: Handling other keys
    19. 🛠️ Calculator: State
    20. 🛠️ Popover: Library
    21. 🛠️ Popover: Adding event listeners
    22. 🛠️ Typeahead: Library
    23. 🛠️ DatePicker: Library
  21. Going from Vanilla JS to JS Frameworks
    1. 🛠️ Building a Tiny framework
    2. 🛠️ Tiny: Add event listeners
    3. 🛠️ Tiny: Updating state
    4. 🛠️ Tiny: Rendering Child Components
    5. 🛠️ Tiny: Changing Parent State
    6. 🛠️ Tiny: Passing Props
    7. 🛠️ Tiny: Multiple Props
    8. 🛠️ Tiny: Passing values from sibling components
    9. 🛠️ Tiny: Mounting
    10. 🛠️ Tiny: Passing props to descendants
    11. 🛠️ Tiny: A tiny refactor
  22. Single Page Apps
    1. What is a Single Page App?
    2. Simple SPA using only CSS
    3. The Location Interface
    4. The History Interface
    5. Minimum viable server for a SPA
    6. 🛠️ Dota SPA: Introduction
    7. 🛠️ Dota SPA: Building The Heroes List
    8. 🛠️ Dota SPA: Building the filters
    9. 🛠️ Dota SPA: Filtering heroes
    10. 🛠️ Dota SPA: Displaying filtered heroes
    11. 🛠️ Dota SPA: Getting Ready to build the Hero Page
    12. 🛠️ Dota SPA: Building the hero page
    13. 🛠️ Dota SPA: Lore and abilities
    14. 🛠️ Dota SPA: Routing for Single-page apps

🛠️ Popover: Adding event listeners

We ended the previous lesson by “breaking” the Popover. If you clicked on each popover trigger right now, nothing happens.

Why? That’s because we haven’t added event listeners to show the popovers!

Let’s fix this by adding event listeners.

Adding event listeners

We have a total of five event listeners:

  1. One to show/hide popovers when users click on their corresponding trigger elements.
  2. One to hide popovers when users click outside a popover
  3. One to tab into popovers
  4. One to tab out of popovers
  5. One to close popovers with the escape key

We’ll work on #1, #3, #4, #5, then back to #2. I saved #2 for the last because it’s a little more complicated than the rest.

Showing/Hiding Popovers

Here’s the event listener we used to show and hide popovers when a user clicks a trigger element.

document.addEventListener('click', event => {
const popoverTrigger = event.target.closest('.popover-trigger')
if (!popoverTrigger) return
const popover = document.querySelector(`#${popoverTrigger.dataset.target}`)
if (popover.hasAttribute('hidden')) {
showPopover(popover)
} else {
hidePopover(popover)
}
})

We can add this event listener into Popover after the Execution phase.

export default function Popover(triggerElement) {
// ...
// Execution
const popoverPosition = popover.calculatePosition()
popoverElement.style.top = `${popoverPosition.top}px`
popoverElement.style.left = `${popoverPosition.left}px`
popover.hide()
// Adding event listeners
document.addEventListener('click', event => {
const popoverTrigger = event.target.closest('.popover-trigger')
if (!popoverTrigger) return
const popover = document.querySelector(`#${popoverTrigger.dataset.target}`)
if (popover.hasAttribute('hidden')) {
showPopover(popover)
} else {
hidePopover(popover)
}
})
}

We can use a named callback to make the event listener easier to read. We’ll call this handleClick since the purpose of this event listener is to handle a click event.

export default function Popover(triggerElement) {
// ...
const popover = {
handleClick(event) {
// Event listener code goes here
},
}
// ...
// Adding event listeners
document.addEventListener('click', popover.handleClick)
}

Improving the event listener

Here’s the code for the event listener right now:

const popover = {
// ...
handleClick(event) {
const popoverTrigger = event.target.closest('.popover-trigger')
if (!popoverTrigger) return
const popover = document.querySelector(`#${popoverTrigger.dataset.target}`)
if (popover.hasAttribute('hidden')) {
showPopover(popover)
} else {
hidePopover(popover)
}
},
}

In the first two lines of handleClick, we searched for the popover trigger from the event. We need to perform this search because we listened to the document element.

We can skip the search if we listened to the trigger element instead – if the callback triggers, we know the user click the trigger element. This method creates more event listeners in the document, but it makes it easier to write code event handlers.

export default function Popover() {
// ...
const popover = {
// ...
handleClick(event) {
// Delete these lines
const popoverTrigger = event.target.closest('.popover-trigger')
if (!popoverTrigger) return
},
}
triggerElement.addEventListener('click', popover.handleClick)
}

In the next line of handleClick, we tried to find popover with the trigger element. We don’t need to find popover anymore because we have popoverElement in the lexical scope.

const popover = {
// ...
handleClick(event) {
// Delete this
const popover = document.querySelector(`#${popoverTrigger.dataset.target}`)
},
}

So all we need inside handleClick is this:

const popover = {
// ...
handleClick(event) {
if (popover.hasAttribute('hidden')) {
showPopover(popover)
} else {
hidePopover(popover)
}
},
}

We already added hidePopover in the previous lesson. We named it hide.

const popover = {
// ...
handleClick(event) {
if (popover.hasAttribute('hidden')) {
showPopover(popover)
} else {
popover.hide()
}
},
}

We can add showPopover to Popover the same way we added hidePopover. We’ll name it show.

const popover = {
// ...
show() {
popoverElement.removeAttribute('hidden')
},
handleClick(event) {
if (popoverElement.hasAttribute('hidden')) {
popover.show()
} else {
popover.hide()
}
},
}

Since if/else statements add cognitive overhead when reading code, we can make things more concise by using a ternary operator.

const popover = {
// ...
handleClick(event) {
popoverElement.hasAttribute('hidden') ? popover.show() : popover.hide()
},
}

That’s it! Let’s work on the next event listener.

Listening to the Tab key

The next two events handle tabbing into and out of Popovers. They both use the Tab key.

// Allows Tabbing into Popover
document.addEventListener('keydown', event => {
const { key } = event
if (key !== 'Tab') return
if (event.shiftKey) return
const popoverTrigger = event.target.closest('.popover-trigger')
if (!popoverTrigger) return
const popover = getPopover(popoverTrigger)
const focusables = getKeyboardFocusableElements(popover)
const shouldTabIntoPopover =
!popover.hasAttribute('hidden') && focusables.length !== 0
if (shouldTabIntoPopover) {
event.preventDefault()
focusables[0].focus()
}
})
// Tabs out of popover
document.addEventListener('keydown', event => {
const popover = event.target.closest('.popover')
if (!popover) return
if (event.key !== 'Tab') return
const popoverTrigger = getPopoverTrigger(popover)
const focusables = getKeyboardFocusableElements(popover)
if (event.shiftKey && event.target === focusables[0]) {
event.preventDefault()
return popoverTrigger.focus()
}
if (!event.shiftKey && event.target === focusables[focusables.length - 1]) {
return popoverTrigger.focus()
}
})

We can create these events in Popover like this:

export default function Popover(triggerElement) {
// ...
document.addEventListener('keydown', handleTriggerTab)
document.addEventListener('keydown', handlePopoverTab)
}

Creating handleTriggerTab

Here’s the code we wrote to handle a Tab on the trigger element.

document.addEventListener('keydown', event => {
const { key } = event
if (key !== 'Tab') return
if (event.shiftKey) return
const popoverTrigger = event.target.closest('.popover-trigger')
if (!popoverTrigger) return
const popover = getPopover(popoverTrigger)
const focusables = getKeyboardFocusableElements(popover)
const shouldTabIntoPopover =
!popover.hasAttribute('hidden') && focusables.length !== 0
if (shouldTabIntoPopover) {
event.preventDefault()
focusables[0].focus()
}
})

We can omit the following lines:

  • Lines 4 and 5 because we have triggerElement in the lexical scope.
  • Lines 6 because we have popoverElement in the lexical scope.

We should have this removing the code I mentioned:

const popover = {
// ...
handleTriggerTab(event) {
const { key } = event
if (key !== 'Tab') return
if (event.shiftKey) return
const focusables = getKeyboardFocusableElements(popoverElement)
const shouldTabIntoPopover =
!popoverElement.hasAttribute('hidden') && focusables.length !== 0
if (shouldTabIntoPopover) {
event.preventDefault()
focusables[0].focus()
}
},
}

When I read through this code, I felt that shouldTabIntoPopover is way too complicated. Since we had two conditions that must be matched, we can make things easier by checking for one condition at a time.

First, we check whether popoverElement is visible. If it is not visible, we will do an early return since its impossible for users to tab into the Popover.

const popover = {
// ...
handleTriggerTab(event) {
const { key } = event
if (key !== 'Tab') return
if (event.shiftKey) return
const focusables = getKeyboardFocusableElements(popoverElement)
if (popoverElement.hasAttribute('hidden')) return
},
}

Next, if the popover contains 0 focusable elements, we don’t let users tab into it as well. We can do another early return.

const popover = {
// ...
handleTriggerTab(event) {
// ...
if (popoverElement.hasAttribute('hidden')) return
if (focusables.length === 0) return
},
}

Finally, we let users tab into the popover.

const popover = {
// ...
handleTriggerTab(event) {
// ...
event.preventDefault()
focusables[0].focus()
},
}

getKeyboardFocusableElements

handleTriggerTab needs getKeyboardFocusableElements to work. I choose to put getKeyboardFocusableElements outside Popover since it’s more of a helper function than a Popover related code.

export default function Popover(triggerElement) {
// ...
}
function getKeyboardFocusableElements() {
// ...
}

Writing handlePopoverTab

The next event listener handles tabbing out of a Popover. Here’s the code:

document.addEventListener('keydown', event => {
const popover = event.target.closest('.popover')
if (!popover) return
if (event.key !== 'Tab') return
const popoverTrigger = getPopoverTrigger(popover)
const focusables = getKeyboardFocusableElements(popover)
if (event.shiftKey && event.target === focusables[0]) {
event.preventDefault()
return popoverTrigger.focus()
}
if (!event.shiftKey && event.target === focusables[focusables.length - 1]) {
return popoverTrigger.focus()
}
})

We can omit the following lines:

  • Lines 1 and 2 because we have popoverElement in the lexical scope
  • Line 4 because we have triggerElement in the lexical scope.

Here’s what we have after omitting the lines above:

const popover {
handlePopoverTab (event) {
if (event.key !== 'Tab') return
const focusables = getKeyboardFocusableElements(popoverElement)
if (event.shiftKey && event.target === focusables[0]) {
event.preventDefault()
return triggerElement.focus()
}
if (!event.shiftKey && event.target === focusables[focusables.length - 1]) {
return triggerElement.focus()
}
}
}

Handling the Escape key

We have an event listener that listens to the Escape key.

// Escape to close popover
document.addEventListener('keydown', event => {
const { key } = event
if (key !== 'Escape') return
const popover = event.target.closest('.popover')
if (!popover) return
hidePopover(popover)
const popoverTrigger = getPopoverTrigger(popover)
popoverTrigger.focus()
})

This event listener closes the popover when users press Escape inside the Popover. Let’s copy-paste this into the Popover.

export default function Popover() {
// ...
document.addEventListener('keydown', event => {
const { key } = event
if (key !== 'Escape') return
const popover = event.target.closest('.popover')
if (!popover) return
hidePopover(popover)
const popoverTrigger = getPopoverTrigger(popover)
popoverTrigger.focus()
})
}

Here are a few improvements:

  • We can omit popover because we already have popoverElement in the lexical scope.
  • We can omit popoverTrigger because we have triggerElement in the lexical scope.
  • We can use popover.hide instead of hidePopover(popover)
export default function Popover() {
// ...
document.addEventListener('keydown', event => {
const { key } = event
if (key !== 'Escape') return
popover.hide()
triggerElement.focus()
})
}

One final thing. We only only want to hide the popover if users press Escape inside the popover element. We can do this by listening to popoverElement instead of document. If we used document, we need to use a closest check to make sure we’re on the right popover.

export default function Popover() {
// ...
popoverElement.addEventListener('keydown', event => {
const { key } = event
if (key !== 'Escape') return
popover.hide()
triggerElement.focus()
})
}

We can put the entire callback into a named function:

export default function Popover(triggerElement) {
// ...
const popover = {
// ...
handleEscapeKey(event) {
// Paste the callback here
},
}
// ...
popoverElement.addEventListener('keydown', popover.handleEscapeKey)
}

Clicking outside the popover

There’s one more event listener to work with. This one closes all popover elements if the clicked target is:

  1. Not a popover
  2. Not a trigger
document.addEventListener('click', event => {
if (
!event.target.closest('.popover') &&
!event.target.closest('.popover-trigger')
) {
const popovers = [...document.querySelectorAll('.popover')]
popovers.forEach(popover => hidePopover(popover))
}
})

There are two ways to write this code:

Method 1

The first way is to copy the code into Popover. If we do this, we create one event listener for every popover instance.

export default function Popover() {
// ...
document.addEventListener('click', event => {
if (
!event.target.closest('.popover') &&
!event.target.closest('.popover-trigger')
) {
const popovers = [...document.querySelectorAll('.popover')]
popovers.forEach(popover => hidePopover(popover))
}
})
}
We added 4 event listeners into the DOM

Duplicated event listeners can be a source of problems if left unchecked.

For example, let’s say you have an event listener that opens or closes a window. If the user clicks once, you open the window. If the user clicks twice, you close the window. In this case, if you had two event listeners running at the same time listeners, you’ll always close the window (because both event listeners will fire).

We can prevent duplicated event listeners by pointing browsers to the same callback handler. This means we have to create a named callback outside of Popover.

export default function Popover() {
// ...
document.addEventListener('click', closeAllPopovers)
}
function closeAllPopovers(event) {
if (
!event.target.closest('.popover') &&
!event.target.closest('.popover-trigger')
) {
const popovers = [...document.querySelectorAll('.popover')]
popovers.forEach(popover => hidePopover(popover))
}
}

Notice we need hidePopover? We cannot use popover.hide because it works only on an instance.

If we want to use popover.hide we need to keep track of all available popover instances in an array. Then, we loop through this array to hide the popovers.

We can do this in three steps.

First, We create the popovers array

popover.js
const popovers = []

Second, we add each popover instance to popovers when we create them.

export default function Popover(triggerElement) {
// ...
// Execution
// Add popover to popovers array
popovers.push(popover)
// Event listeners
}

Third, we loop through the popovers array and hide each popover.

export default function Popover() {
// ...
document.addEventListener('click', closeAllPopovers)
}
function closeAllPopovers(event) {
if (
!event.target.closest('.popover') &&
!event.target.closest('.popover-trigger')
) {
popovers.forEach(popover => popover.hide())
}
}

Method 2

The method above is the “most technically correct” way to create global event listeners for multiple instances. But it can be complicated if you’re not used to it.

If you don’t have lots of instances on the same page, performance doesn’t really suffer, so we can use an alternate method to close popovers.

In this case, we’ll add the event listener inside Popover.

export default function Popover() {
// ...
document.addEventListener('click', event => {
// ...
})
}

We can then check whether the event target is within popoverElement or triggerElement. If they aren’t in any element, we hide the popover.

export default function Popover() {
// ...
document.addEventListener('click', event => {
const target = event.target
if (
target.closest('.popover') !== popoverElement &&
target.closest('button') !== triggerElement
) {
console.log('hello')
popover.hide()
}
})
}

This creates an effect where only one popover can be active at one time.

That’s it!