fork/Graphite
1
0
Fork 0
mirror of https://github.com/GraphiteEditor/Graphite.git synced 2026-09-24 08:28:11 +08:00
Code Issues Packages Projects Releases Wiki Activity

Fix website rendering issues on Firefox with -webkit-line-clamp

Browse Source
This commit is contained in:
Keavon Chambers
2022-05-12 14:22:43 -07:00
parent 15641a3d2a
commit 6cae6b54b7
4 changed files with 15 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
website/content/contribute/_index.md
+1 -1
View File
@@ -71,7 +71,7 @@ The actual document (the artwork data and layers included in a saved `.graphite`
Every part of the Graphite stack works based on the concept of message passing. Messages are pushed to the front or back of a queue and each one is processed by the module's dispatcher in the order encountered. Only the dispatcher owns a mutable reference to update its module's state.
<details><summary><b>Addition technical details (click to show)</b></summary>
<details><summary><b>Additional technical details (click to show)</b></summary>
A message is an enum variant of a certain message sub-type like `FrontendMessage`, `ToolMessage`, `DocumentsMessage` (plural), or `DocumentMessage` (singular). An example is `DocumentMessage::DeleteSelectedLayers` (which carries no data) or `DocumentMessage::RenameLayer(Vec<LayerId>, String)` (which carries a layer path and a string as data).