Bug: Extension does not work for local files loaded with the `file://` protocol.

Open
#21 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
tailwindcss
Domain
devtools

Research direction

Reproduce this with a local file in Chrome, then start at the DevTools for Tailwind CSS panel activation flow. Trace why activation remains pending for file:// pages; done means the panel loads, supports interaction with Tailwind on the file, and no longer remains on the activation message.

Written by the indexing model from the issue text.

Description

Steps to reproduce:

  1. Load a local file (file://) in Google Chrome with this extension enabled.
  2. Open DevTools and navigate to the Devtools for Tailwind CSS panel.

What is expected:
The extension panel loads and allows interaction with Tailwind on the file.

What happens:
The message "Activating DevTools for Tailwind CSS..." is displayed and never changes. There is no observable error message printed to the console.

Dominant language
No language data
Stars
5
Forks
0
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from beyondcode/devtoolsfortailwind-community

All issues in beyondcode/devtoolsfortailwind-community

Similar issues

More DevTools issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.