11/24/2023 0 Comments Overflow x not working![]() ![]() The second issue is when i am trying to add more try and excepts (to handle date time (YYYYMMDDHHMMSS+ TIMEZONE) i get the error: Synta圎rror: too many statically nested blocks. The function works as intended while passing my own list, but it doesnt work when applying to DATAFRAME? if _name_ = "_main_": The first issue is when im applying this function using df = df.apply(func=date_handler) RESOLVED: Allow 2 values on the overflow property in physical x/y order in any existing values.Imn trying to write a function that will handle dates in a given format however, i'm having a few issues. rune_: If you have visible overflow in x and y you get visible. astearns: People use overflow x and y in various situations and it' sjust that it would be nice to let them use the shorthand for both. myles: What a combo authors want with different keywords? astearns: Prop: Allow 2 values on the overflow property in physical x/y order in any existing values. astearns: Anyone have a concern with allowing whatever combo we spec? Anyone object to taking what we get and stransform? emilio: Outline style stuff which when you have hidden outline and the line-width becomes 0. fantasai: Almost for display but we made all combos invalid. florian: Stylesheet maintenece it's strange. astearns: I'm not certain having a transofmr apply implies there's a problem in your stylesheet. emilio: fantasai Tranforming em to pixel doesn't show you've got a problem in your style sheet. astearns: Computed value shows something changed. fantasai: Would be nice if a validation pool flagged this. dbaron: CSS ties to reject things that don't make sense. florian: Makes sense when you transform. dbaron: Reject things that don't makes sense. fantasai: If you serialize out computed values it's valid. florian: I don't think we gain by forbidding these. astearns: I would prefer let ou set the shorthand to whatever and letting it transform. florian: You have a minifier and it takes the 2 longs and puts them to short and that's a parse error. myles: You set the shorthand and it's rejected and that's different that if you set the 2 longhands. emilio: I think it would be weird if spec shorthand would yield different results. ![]() Do we want the things that are not going to be valid in the end be parse errors? dbaron: I guess it's not really a serialization problem. Because then values could not serialize to short hand I'm thinking a it would be nice if it rejected but b it's not possible because serialization problem. dbaron: Transofrmation would still happen. myles: Related that this shorthand shouldn't allow new functionality Should those combos be syntatically valid for shorthand? If x is visible and y is scroll we make scroll into auto. dbaron: Quesiton: There are sets of values transofrmed into other values. astearns: Prop: Allow overflow to have two value and for the ordering to be physical. florian: A more consistant system where they all have shorthands and they're physical. florian: I suggest we presume that's rare and if it's a problem we raise it astearns: Weird mistyped decalrations may now have an effect? astearns: Separate from that switch, do we let overflow accept 2 values? florian: Other is issue #1282 which discussed adding logical keyword to all places currently phsycial. ![]() There's another issue looking to switch longhand and shorthand into phsycial order. As an example background-position is x and y. Then there was the question is the order should be physical or logical. ![]() It would be more convenient if it accepted two values. Oriel: It only lets you set overflow-x and overflow-y.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |