desandro / close-pixelate Goto Github PK

Is there anyway of manipulating close pixelate for implementation with the CSS background-image?

Alax, 'forging' images with the maxnov hack no longer works. Perhaps because the API request limit was maxed out. In any case, the scope of the script should be scaled back to just same-domain images.

Yes: The final standard can be found here: https://github.com/ethereum/EIPs/blob/master/EIPS/eip-20-token-standard.md

Originally posted by @frozeman in ethereum/EIPs#20 (comment)

I can't specify target width and height of rendered pixelated image.

I can't apply filter to existing canvas element (where i actually can draw the image with the dimensions i want it to be).

Background

Back in #3943, we started rendering text editor contents inside a shadow DOM boundary to prevent outer style sheets from altering the editor inner contents. Although this introduced many benefits, it carried several tradeoffs too.

In particular, we started duplicating some of the style sheets ({context: 'atom-text-editor'}) inside each shadow root so that package and theme authors could still be able to explicitly target the editor visual elements. An alternative solution to this problem that we suggested (before the shadow DOM spec was finalized) was to use /deep/ and ::shadow pseudo selectors, which unfortunately are now being deprecated.

Even more importantly, this architecture was getting in the way of making atom-text-editor a reusable component, because it made it even more coupled to Atom and its ecosystem. Other problems involved things like #4590, and a more complex user experience for package and theme authors in general. Ultimately, we started feeling like the extra complexity of the shadow DOM wasn't worth its benefits.

Removing shadow DOM from atom-text-editor

This pull request aims at removing the shadow DOM in a way that prevents elements within atom-text-editor that we don't fully control (i.e. the grammar scopes applied as CSS classes to every line's inner <span>) from being mistakenly styled from the outside. Specifically, every syntactic class name will now be prepended with syntax--; styling a JavaScript operator, for example, should now look like the following:

.syntax--source.syntax--js .syntax--operator {
  color: green;
}

Given the wide scope of this change, we are trying to reduce package breakage to a minimum by transforming deprecated selectors automatically and emitting a deprecation in deprecation-cop. Applying these transformations can be quite onerous and therefore we have introduced a layer of caching in 07d56b2 to ensure their performance impact stays low after the first time Atom is launched.

Other notable changes include:

• Block decorations rendering has been rewritten from scratch (it previously worked only with the shadow DOM).

• When the editor is focused, document.activeElement will now return the hidden <input> inside atom-text-editor, instead of atom-text-editor itself. I could find only one third party package relying on this behavior, and I am going to submit a pull request shortly to use document.activeElement.closest('atom-text-editor') instead.

• Any Grim or style sheet deprecation will now cause specs to fail, see ensureNoDeprecatedFunctionCalls and ensureNoDeprecatedStylesheets.

• Rendering flashes for decorations has been broken for a long time, but removing the shadow DOM highlighted the cause of the issue, and so they have been fixed in 1091b0e.

  

Conclusion

Removing the shadow DOM is an important step for the editor's future, as doing so will allow us to extract it, clean it up and optimize it. Considering the invasive nature of this change, we are planning to 🚢 it after rolling the railcars next week, so that everyone can build it from master and extensively test it for an entire release cycle.

Before merging this, we will also need to merge the following core package pull requests, so that we stop using any deprecated API or selector, and make the test suite green again:

• ⬆️ autocomplete-plus (atom/autocomplete-plus#779)
• ⬆️ autosave (atom/autosave#71)
• ⬆️ atom-dark-syntax (atom/atom-dark-syntax#31)
• ⬆️ atom-dark-ui (atom/atom-dark-ui#64)
• ⬆️ atom-light-syntax (atom/atom-light-syntax#9)
• ⬆️ atom-light-ui (atom/atom-light-ui#36)
• ⬆️ base16-tomorrow-dark-theme (atom/base16-tomorrow-dark-theme#31)
• ⬆️ base16-tomorrow-light-theme (atom/base16-tomorrow-light-theme#11)
• ⬆️ bookmarks (atom/bookmarks#70)
• ⬆️ command-palette (atom/command-palette#72)
• ⬆️ deprecation-cop (atom/deprecation-cop#70)
• ⬆️ find-and-replace (atom/find-and-replace#789)
• ⬆️ git-diff (atom/git-diff#111)
• ⬆️ markdown-preview (atom/markdown-preview#436)
• ⬆️ package-generator (atom/package-generator#45)
• ⬆️ one-dark-syntax (atom/one-dark-syntax#79)
• ⬆️ one-dark-ui (atom/one-dark-ui#168)
• ⬆️ one-light-syntax (atom/one-light-syntax#24)
• ⬆️ one-light-ui (atom/one-light-ui#77)
• ⬆️ settings-view (atom/settings-view#862)
• ⬆️ solarized-dark-syntax (atom/solarized-dark-syntax#76)
• ⬆️ solarized-light-syntax (atom/solarized-light-syntax#26)
• ⬆️ wrap-guide (atom/wrap-guide#60)
• ⬆️ apm (atom/apm#615)
• ⬆️ first-mate (atom/first-mate#80)
• 📝 Update the flight manual (atom/flight-manual.atom.io#281)

/cc: @atom/core

__Originally posted by @as-cii in https://github.com/atom/atom/pull/12903__exit
Push