Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upRename compartment-related terminology to use realms instead #25581
Comments
|
Hi! If you have any questions regarding this issue, feel free to make a comment here, or ask it in the If you intend to work on this issue, then add |
|
@highfive: assign me |
|
Hey @kunalmohan! Thanks for your interest in working on this issue. It's now assigned to you! |
|
@jdm should servo/components/config/prefs.rs Line 380 in d0d3aaa be renamed too? |
|
It turns out that preference can be removed; we don't actually use it anywhere in servo. |
|
Can you explain (or provide a resource) what role preference values play and why don't we need it anymore? Are they, in any way, related to user preferences and how users want servo to operate on their system? I don't have much idea what it means here at this point Line 65 in 592649b And in the above comment, we are talking about removing just the 'per_compartment', right? |
|
Ok, I think I get it. prefs.json sets the values for various limits and functionalities that servo should follow/use by default, right? (I think I have put it in a very vague manner) |
|
There are no uses of |
|
And yes, the values in prefs.json are read during Servo's startup and used for configurable values in Servo's code. |
|
Ok. I have renamed the variables, functions, structs, etc. in |
|
Yes please! That will require changing https://github.com/servo/servo/blob/master/components/script/dom/bindings/codegen/CodegenRust.py#L3400-L3401 and as well. |
|
Agreed. All of those need to stay. |

This is specifically about
components/script/compartments.rsand names like AlreadyInCompartment. Everywhere we use the name compartment, we should use the name realm instead.