Ryo Kamei

I would like to know the following. * Is the fix acceptable? * Is there a better way than sharing the same CSS? Please let me know if I made...

Thank you for your review. `_cascaded_styles` is a simple fix because it is disposable to create `_computed_styles`. For example, it was difficult to pass the test in the area you...

Sorry, I did not read [the article](https://hacks.mozilla.org/2017/08/inside-a-super-fast-css-engine-quantum-css-aka-stylo/). I don't know if I can do it, but I will try the following first. > In Quantum CSS, we gather up all...

Thanks for the continued support. I have also tried modifying the ComputedStyle, but I am getting errors in the following three cases. I would appreciate if someone could give me...

I'm sorry. The test case we compared was incorrect. The reduction is about 23%. The slow deepcopy is causing the execution time to increase significantly. I will try to improve...

Table: 2500rows | | mem | sec | | :--- | ---: | ---: | | | 830MB | 120.99 | | After change | 638MB | 258.01 |

As far as the distribution of memory specifications is concerned, as confirmed by the document.py _render method, the larger the table, the more memory usage will approach 1/3 of the...

I also tried AnonymousStyle sharing. It still could not be compressed better than the others. I would like ideas to reduce the number of saves with the current system to...

Significant memory compression is expected for large tables. I consider execution time to be an issue. Table: 13000rows | | mem | sec | | :--- | ---: | ---:...

For ComputedStyle with the same cascading style index, would it reduce processing if I could mark it as computed, or would that not be very effective since it would have...