25 Matching Annotations
  1. May 2021
  2. Apr 2021
    1. .mainContent {  -webkit-user-select: none; -moz-user-select: none; -ms-user-select: none;  user-select: none; }

  3. Mar 2021
  4. Feb 2021
  5. Jan 2021
  6. Dec 2020
  7. Oct 2020
  8. Sep 2020
    1. DX: start sapper project; configure eslint; eslint say that svelt should be dep; update package.json; build fails with crypt error; try to figure what the hell; google it; come here (if you have luck); revert package.json; add ignore error to eslint; Maybe we should offer better solution for this.
    2. When the message say function was called outside component initialization first will look at my code and last at my configuration.
    1. Svelte will not offer a generic way to support style customizing via contextual class overrides (as we'd do it in plain HTML). Instead we'll invent something new that is entirely different. If a child component is provided and does not anticipate some contextual usage scenario (style wise) you'd need to copy it or hack around that via :global hacks.
  9. Jul 2020
  10. Jun 2020
  11. May 2020
    1. This is it. I'm done with Page Translator, but you don't have to be. Fork the repo. Distribute the code yourself. This is now a cat-and-mouse game with Mozilla. Users will have to jump from one extension to another until language translation is a standard feature or the extension policy changes.
    2. If any Firefox engineers are reading this, please don't try to subvert the above workaround, it requires multiple steps and administrator rights to set up, and we must all agree that it is of little sense for Firefox to try defending against unwanted programs or malware that has root access on the device.
    3. Mozilla will never publicly ask users to circumvent their own blocklist. But it's their actions that are forcing people to do so.
    4. So to me, it seems like they want to keep their users safer by... making them use Google Chrome or... exposing themselves to even greater danger by disabling the whole blocklist.