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 upMove overflow-y outside of Mako #19183
Comments
|
@jdm |
|
@olmanz I believe @PeterZhizhin is already working on this. |
|
Yeah, note that this one is actually extra-tricky. |
|
@PeterZhizhin Do you need any help? Any questions? |
|
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 |
|
Unassigning due to lack of response. This issue is now open for anyone to work on! |
|
@highfive: assign me |
|
Hey @olmanz! Thanks for your interest in working on this issue. It's now assigned to you! |
|
@KiChjang @emilio However, I currently get this message when I build servo with
I found out that the file /target/debug/build/style-fe2cedc35103ef47/out/properties.rs is created by components/style/properties/build.py, but I'm not quite sure how to get rid of this error message. |
|
I think the root cause is the The servo/components/style_traits/values.rs Lines 388 to 416 in b7bb6ff The servo/components/style/macros.rs Lines 107 to 127 in b7bb6ff Thus, when the servo/components/style/properties/helpers.mako.rs Lines 36 to 48 in b7bb6ff it will generate the file with So, all you need is passing needs_context=False in You can reference to |
|
Thanks, that worked! |
|
Pull Request is out. |
|
The previous author is busy in school right now. If anybody would like to tackle this, it is available. See #19448 for prior work. |
|
I'd like to work on this one if it's still open! |
|
@nicknadeau Please do! |
|
So I've done some investigating and just want to make sure I understand correctly. |
|
It's a combination of changing those mako lines to use predefined_type, as well as extracting the actual types that used to be generated by mako into proper Rust definitions in style/values, and ensuring that |
|
Hi @nicknadeau, have you managed to make any progress on this? Thanks! |
|
Hi @emilio, progress has been a little slow, just got out of midterms. I'll be giving this bug a go over the next few days and I'll update my status by mid-late week and let you know if I have any questions. I hope that's alright, sorry for the slow start. |
|
Sounds great, no worries, and thanks! :) |
|
Ok I've started out on a similar foot to olmanz and used overscroll-behaviour as an example to mimic. I'm just stuck here, I'm really not sure how to deal with some of these params. For instance, I've tried sending gecko_constant_prefix into predefined_type and I get: So I'm wondering, am I trying to get things like gecko_constant_prefix, custom_consts etc. into predefined_type as well? Is it appropriate to use the single_keyword function to handle the gecko stuff? Sorry, still trying to understand how the code is working. |
|
maybe someone removes E-easy label ? judging by history it's "anything but" easy |
|
Well to be fair I've only spent ~2 hours on this so far, I'll keep tracing things and see what I can figure out. |
FWIW, it should be easier now, the relevant prerequisites have already landed, like #19578. |
Sorry I missed this before, you should stop using |
|
My progress so far: In gecko build I get the following error coming from set_overflow_y in gecko.mako.rs
|
|
I'm sorry guys, I really don't know how to progress from here, I don't understand enough of this code base in terms of the gecko stuff |
|
@emilio This is probably going to need your attention to answer the previous question. |
|
Oh, sorry, thanks! @nicknadeau: So that error means that |
|
I think this was effectively done in https://bugzilla.mozilla.org/show_bug.cgi?id=1470695. @jdm do you have any other potential good first issue for @PhilParisot? |
I think that this should be an easy property to start with. This is a sub issue of #19015.