Tasks that require more thinking/input from community to reach an decision for the most suitable implementation.
Not to be confused with Clarification Needed - to be used when the general background is unclear or partially Invalid.
Tasks that require more thinking/input from community to reach an decision for the most suitable implementation.
Not to be confused with Clarification Needed - to be used when the general background is unclear or partially Invalid.
Another good simple candidate GDPR-friendly:
In T15670#16064, @valerio.bozzolan wrote:A root problem is that highlighted line number(s) should be a # fragment really, to do not multiply pages exponentially.
A root problem is that highlighted line number(s) should be a # fragment really, to do not multiply pages exponentially.
In T15728#15768, @valerio.bozzolan wrote:I tried to understand the situation. Thanks.
In your opinion: on the repo view (with clone buttons) is it really important to link to the other similar "reduced" view (without clone buttons)?
I tried to understand the situation. Thanks.
I agree, disabled users should be hidden in the global search typeahead results.
In T15736#15681, @bekay wrote:
- Get rid of the JX namespace and the the require comments - use import and export like it is done in modern js
I'm not against replacing the mechanism - It's just that the original task description doesn't specify why that would be good (i.e., what the benefit would be).
That's clear from the discussion now, but should generally be included in the ticket description - the "describe "what", not "how"" principle.
A big benefit of using client-side variables in CSS, is that one can use the browser's prefers-color-scheme media query to select light or dark mode based on the user's browser or system setting, automatically, and that the transition from light to dark mode, or to other accent/highlight color schemes, requires no reload.
Well, I see a tremendous critism and scepticism concerning modern client side techniques here. The world of frontend tooling has changed tremendously in the last 5 years. And I understand concerns, but nobody has to write JavaScript for certain browsers anymore. Javelin for example tries to solve so many problems that Babel solves with one config entry. But that's okay and I like the architecture here and know we can't change everything at once.
Ok, I don't understand the specifics of css-vars, but if they're better, they're better.
The overwriting of variables with media queries could be configured inside the theming class. So possible breakpoints can be part of a theming API.
And my general approach is: when the client can do something (and that even better), why should the server do it?
@avivey CSS vars are a vital part of modern modularized theming. They are versatile, can be overwritten with media queries or per class/element basis. They are editable in browser dev tools. If you would ask me: this step is pretty important.
In T15736#15726, @avivey wrote:to have a working dev server when developing js - at the moment I have to ./bin/celerity map after every change to js and css to see my changes...
Are you sure about that? I thought celerity map was only needed when adding a file (in dev mode).
also, adding this file in src/extensions/ will let you have css/js files from src/extensions/rsrc/ loaded automatically:
to have a working dev server when developing js - at the moment I have to ./bin/celerity map after every change to js and css to see my changes...
Looks to me that the existing system is better at providing Themes? It allows real code, inheritance, etc. to set variable values.
That is, I think Extension Themes are better off writing PHP Post-Processor rather then CSS vars.
I don't know if that is part of this task, but the global typeahead search should hide all disabled users, wikis and repos, shouldn't it? This is nothing you want as a fast suggestion...
Well, my idea would be:
When I was at Wikimedia I remember a lot of issues from search robots endlessly indexing dynamic pages.
In case of what?
OK. Then we can add a Task about how to easily configure robot changes without forking, in case.
Thinking more, I think we'd like to allow the robots to index latest version of the code - these days the big boys know how to handle that. Stopping them from crawling older versions is still important.
So apparently the ferret search engine doesn't really have any sort of dynamic ranking. The ranking is entirely based on how many ngrams match the query...with one singular exception - all user results are boosted above everything else.
I'll try to figure out a architecturally-appropriate way to do this. The users do get grayed out in the typeahead search, just not on the results pages.
Partially related, from the mentioned search it's easy to recognize closed Tasks, but Users are not greyed out when Disabled.
User content is also content, thus yes.
Good question. Maybe also related to L2.
Is it assumed that using the site will automatically license the user’s content under these, or should there be a line for that?
In T15322#15031, @aklapper wrote:+1 on Content licensed under Creative Commons Attribution-ShareAlike 4.0 (CC-BY-SA) unless otherwise noted; code licensed under Apache 2.0 or other open source licenses.
Values given in em units may produce unexpected results...