"Component is not available" nsresult: "0x80040111 (NS_ERROR_NOT_AVAILABLE)"

Open
#481 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript, typescript
Domain
frontend

Research direction

Start by reproducing the reported compatibility issue in Firefox 60.7.0esr using the code shown in the issue, then locate the relevant utility entry point and existing browser tests. Done means the Firefox error is addressed without regressions and the proposed change has a clear maintainer-approved path into the master branch.

Written by the indexing model from the issue text.

Description

I found some compatibility issues in Firefox browser.

Environment
Browser: Firefox 60.7.0esr (64 bit)
Browser download link: ftp.mozilla.org/pub/firefox/releases/60.7.0esr/

I try use these codes to fix this issues:

var _getComputedStyle = getComputedStyle(target, '::-webkit-scrollbar');
var width = '0px';
var height = '0px';
try {
    width = _getComputedStyle.width,
    height = _getComputedStyle.height;
}catch(e) {
    width = '0px';
    height = '0px';
}

Can these codes be merged into the master branch?

Dominant language
TypeScript
Stars
670
Forks
205
Avg merge
15d 17h
Merged PRs (30d)
6

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 react-component/util

All issues in react-component/util

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.