The position of the "remove" tool is inconsistent between "initial" and newly-uploaded files. See this partial screenshot:

The left image is newly-uploaded, with the "remove" tool on the right, while the right image is an "initial" file with the "remove" tool on the left.

I suggest t

Repro

{
  "rules": {
    "@typescript-eslint/prefer-readonly": "error"
  }
}

interface Config {
   num: 40
}
const config = {
  num: 40
}

class myClass {
  private num: number; // 1
  constructor() {
    this.num= 

As the reverse plugin was removed and the suggestion was it's possible doing with template, I did my best to take a stab at it. It's currently still a WIP so as I don't handle subnets yet.

Also I assume that I'm missing something here. Feels too manual for reverse lookups even with template.

One can also use 0.8.e.f.ip6.arpa 127.in-addr.arpa (sidenote: fe80::/10 doesn't fully map to 0.8.e.f.

Is a :page parameter validated?

If I change :page to non-numeric value I got the exception. I think that should be treated as 1

Being a newer user to vue-i18n, I accidentally was using the unsafe v-html binding solution after reading the docs on HTML Formatting. Going back through the docs, I now noticed the big warning at the top suggesting using component interpolation.

What do you think about showing an example of component interpolation under the HTML formatting section (https://kazupon.github.io/vue-i18n/guide/fo

Expected behavior:

When opening a preview with `p

这边需要在 debug 模式下做一些特定的处理，发现 BuildConfig.DEBUG 一直都是返回 false ，试过修改 gradle 配置，assembleDebug 都不行。

    if(BuildConfig.DEBUG){
      // Debug 模式下添加日志打印
      clientBuilder.addInterceptor(new HttpLoggingInterceptor(new OkHttpLogger()).setLevel(HttpLoggingInterceptor.Level.BODY));
    }

如果能在 Small 中加个 isReleased() 方法判断是否在发布环境是不是会比较好？或者有其他更好的处理方法？

Are you aware of any different behavior when a PWA (using offline-plugin) is added to the home screen using "Add to Home Screen" on Chrome/Android or Safari/iOS?

I'm having problems with the app getting stuck using the cached version when it was installed and never updating.
I even have offline-plugin responseStrategy set to network-first but it seems to always use the cached version after add

JS 配置如下：

 var gitalk = new Gitalk({
            clientID: '3654916*****0c0038c28',
            clientSecret: 'd90d031a*****0e0fa4c7fe2fae747b96b',
            repo: 'Strange-AI.github.io',
            owner: 'Strange-AI',
            admin: ['jinfagang', 'Strange-AI'],
            id: vm.codeId,
            distractionFreeMode: false
        });
        gitalk.render('gitalk-conta

This issue relates to #180.

What you did:

1. open example from doc in 2 tabs
2. increment counter 4 times in 1st tab
3. increment counter 1 time in 2nd tab
4. refresh both tabs

What happened:
Increment from 2nd tab overrides actual state from 1st tab.

Reproduction sandbox:
https://codesandbox.io/s/80k4m2598

Suggested solution:
Would be nice

Please add an option to disable it to give users more control over what gets matched, we need this for a project where we need to limit height matching to what we define only.

Thanks

this would be a nice option for sidr, instead of moving everything opposite the sidr menu, it will instead resize its content container while showing the sidr menu

Is there a reason for having the JS component tick interval hardcoded to 30 milliseconds.

Would be nice to be able to change/disable this in the details panel.

Version : 1.0.14

First, thank you for this tool, it is really useful.

The issue I am having is that the circle in the overview page is too small, around a quarter of its normal size.
It wouldn't be such a problem if is it wasn't for the text overlapping the inner most circles-dependencies.

For the record, I am using webpack through Karma, but I don't think it is relevent for this issue

According to MDN, CustomEvent is not supported in IE. But this is not detected by the plugin.

Example code

// it should throw an error here, but it doesn't
const event = new CustomEvent("cat", {
  detail: {
    hazcheeseburger: true
  }
});
window.dispatchEvent(event);

Trying to find a viable fix for this but struggling so far. I'd appreciate if someone else could pitch in...

The top margin on the first element and bottom margin on the last element are not effective on Firefox. However, they are in Chrome - which causes some spacing inconsistencies. This is more noticeable when there's enough content to fill the containing <div> and trigger a scroll bar.