Fri, Sep 9
Tue, Aug 30
I was thinking a lot about this ever since we talked about this problem, and so I would like to offer a slight point here about being careful of over-optimizing for this problem.
Jul 20 2022
Unfortunately, I'm in the same boat; I've never actually been directly involved in the project. I had a very passing general interest in it while working on another GraphQL project -- and I worked with the original maintainer! -- but I don't think I can serve as a maintainer on this (or even fix bugs...)
Apr 1 2022
Mar 14 2022
Feel free to share those wherever you deem fit :)
Mar 10 2022
Mar 9 2022
Another example for what I was trying to demonstrate is the "flipping" of the expected location of the negative sign
This figma file is absolutely incredible. For years we've been working on RTL support on the Wikimedia projects with some learnings and insights that were very rarely properly coalesced into a proper document with guidance and decisions, so having one being worked on not only as decisions for the specific Codex library, but as more widespread visual guidance is extremely helpful!
Feb 16 2022
Icons and RTL are one of my favorite topics of philosophical musings that lead to practical visual decisions -- but they're usually really complicated, as the discussion here demonstrates.
Jan 9 2022
Jan 8 2022
I'd love to try, but this is an interesting problem... I admittedly did not have a chance to go over any of the code yet, so I'm mostly offering some guesses here for now based on previous experience.
Dec 15 2021
Not only is netlify self hostable, it directly connects to a github repository and gives you a myriad of deploy tools, including an automatic pull request preview, A/B testing with two or more branches, deploy out of a specific branch, etc.
Dec 2 2021
Ah, localizing filenames on wiki, yes. One of the toughy questions, honestly.
Nov 15 2021
(Add) -- also, you'll need to take into account the ability to let component users (implementers?) force directionality for content (so, input direction regardless of interface) and also force and set based on interface. I know we all know this, I'm just pointing it out because it might get a bit more complex with the prefix selectors.
This sounds generally good plan, I'm slightly worried about how exceptions may work with logical properties, but I think they should work in general.
Sep 13 2021
Sep 3 2021
There's a lot of really good questions in this thread that are more about the general knowledge store than they are specifically about the data model (so just pointing out potential scope creep of the ticket specifically regarding the DSO) *but* I have some general points that I thought would be useful to raise in this context too.
Aug 11 2021
Another clarifying point is that this isn't about changing our internal nomenclature "deep inside our stack" - this is a solution that's meant for clients like Wikimedia Enterprise and a distribution method to provide a layer between the information we have in our databases that uses terms and nomenclature that are very specific to the Mediawiki operations, and translate that to consumers who want to digest pieces of the data using as much commonly "human digestible" terminology and structure as possible.
Jul 7 2021
Jun 30 2021
Yes to all of the above -- we definitely want to make sure we're iterating on a data model, and it's definitely important to decide on the standard. We do have a couple of artifacts touching on this and we'd love to share those.
We should make sure we choose a library that properly supports RTL. It seems Tailwind has support, but potentially a bit over complicated, see: https://github.com/tailwindlabs/tailwindcss/discussions/1492#discussioncomment-6061
Jun 14 2021
To be honest, my main pet peeve is that mediawiki is taking a choice that the user usually thinks is private (preferences), that is then used to show things differently only for them in their context - and then turning around and using it publicly.
Gender, sex, and language pronouns are three distinct notions. The article discusses some application of this, but the first sentence can't be clearer:
A gender symbol is a pictogram or glyph used to represent biological sex and gender in biology or medicine"
Jun 13 2021
Jun 11 2021
Jun 10 2021
Jun 9 2021
This is a fascinating discussion and I actually am not entirely sure I have a good answer to this. As a woman who speaks gendered language, this touches all my pet peeves at once, which would have been helpful to formulate an opinion, except some of those pet peeves are from one side and the others on the other.
May 26 2021
May 14 2021
From my personal perspective, and my experience with OOUI that was meant to be a shared library used by teams to create components, I am extremely intrigued by the potential benefits that TypeScript can offer with the IDE hints and developer-help that you've mentioned above. I think it might be worth exploring whether it's worth using TypeScript if not in the entire wvui library, then even only on the "lower/common" underlying code that others will rely on -- llike mixins and base components.
Jan 7 2021
I am not sure if you've done anything in the past couple of days, but I haven't encountered this issue anymore.
Jan 3 2021
Dec 7 2020
Re your notes, in reverse order:
Oct 28 2020
Oct 25 2020
Chrome and FF seem to be somewhat smart about the date and are rendering it properly in RTL
Oct 11 2020
Oct 9 2020
Oct 1 2020
Sep 30 2020
Honestly beyond the awkward connotation (!) in that name, I'd offer that the name of the product should be more descriptive of what the product actually does. This product is available especially to people who are not familiar with wiki-speak, who come in and want to export pieces of text, books, etc, to standalone formats. Changing the name to reflect the use and purpose of the tool can be beneficial on top of the fact that we should really avoid sticking to very awkward connotation from the abbreviation.
The idea here is that since the global watchlist contacts the individual Wikipedias' APIs, we want to limit how many concurrent requests are sent, because sending a request to 900+ apis is unreasonable.
Sep 28 2020
Note: I sent the draft document link directly to @srodlund
Sep 10 2020
I'm jumping in (by request! ;) to give my recommendation: I would 100% go with VueJS on this, even only for the reason that recently this was the framework adopted by the foundation for our frontend modernization.
Jul 21 2020
Also, this shouldn't act as a gadget; we did not officially release it as such and it is not optimized to be that. We're supporting it as a browser extension, and we're (ab)using the ResourceLoader queue "feature" to insert ourselves as if we're a gadget,but still working from the browser.
IIRC, we need to ask for the translated message for the button/link, and while we're at it we're asking for the rest of the messages. I don't think we can get away with not calling it at all and still have the link appear? (though admittedly I need to delve into the code again to see if it's a timing issue)
Jul 8 2020
Jul 7 2020
Jun 30 2020
@Marostegui (feel free to tag anyone else that may need to participate here?), we've discussed this extensively in the team after running into some challenges, and ran some analysis on the usage of the watchlist table. We want to see if we can reframe the problem and make sure we can find a viable way forward.
Jun 29 2020
Another idea, followup from conversations in the team:
May 29 2020
There's an issue here we should account for, or at least be aware of, that may make this block action less impactful than we'd think. If we go with @DannyS712 idea, we could probably block the actual action of moving a page (when you hit the menu action item for "move") but there are other ways to move pages manually.
May 22 2020
May 21 2020
It looks like the output should be added to the table entry for the page rather than just the rows outputted for a single change, in "EnhancedRecentChanges". Good catch, @Scardenasmolinar
May 20 2020
May 19 2020
May 15 2020
We definitely rely on user rights when we show (and not show) the information when a revision is suppressed or deleted, by feature (not bug) so it sounds reasonable that if the revision was deleted, you'd get a popup with hidden details.
Can you check if this happened at a specific revision? I just tried it now, and I see the entire text highlighted, given credit to your username as have written 100% of the page.
May 14 2020
May 8 2020
May 7 2020
May 5 2020
May 1 2020
Sure, but there are exceptions to this rule, and when those exist, we do need a way to do it.
I think that the question of which "upstream" is a good one; ideally, this actually could be generic enough to be in OOUI tiself, but I agree that it probably just increases complexity and size for probably very low usage.
That's weird; we do have inline forms with text fields, I'd have expected this to be found as a bug before.... :\
If FieldLayout allows for an inline config, then it should respect inline settings.
Apr 21 2020
After a bit of back and forth with @Catrope and examining the challenges here with an OOUI popup, Roan made a good point about at least testing whether the alternative is viable.
Apr 17 2020
Thank you everyone for all the feedback and back and forth, and I apologize for any misunderstandings here.
Apr 9 2020
Apr 7 2020
@Nuria I'm a little confused, and I'd like to clarify something.
Mar 31 2020
Split to two tickets:
(egh, my screenshot didn't work, but--) w00t, it works now!
Sweet, I think this should fix it. I +2'ed, so it should be available on beta soon to test.
Mar 27 2020
Following up since @Etonkovidova has asked me to look into why it's not working:
Mar 24 2020
Mar 22 2020
I would avoid doing things that have no (or huge) limit. Honestly, I think it's a product problem more than a performance one, but since we are checking more than one target (unlike the original) I'd be slightly more careful, and go with pagination.
Mar 13 2020
Mar 12 2020
This looks great. Let's just make sure we don't literally copy over what RecentChanges is doing, because the way it is constructing its lines is pretty horrific, and uses monospace-font single-spaces to align tags per each line, etc.
Mar 7 2020
Oh, I'm sorry if I misrepresented. I got confused with the table showing different messaging exists=true and exists=false... which is different than the suggestion. Sorry, it's really confusing -- I'm just glad we are on the same page!
My main concern was about changing the behaviour of a long-standing and widely-used widget - if that's ok then let's go ahead with this.
Mar 6 2020
Thank you for the thorough analysis, @Tchanders !