I'm a big fan of moving this RFC forward... On our end, we have internally deployed the solution described in Proposal 2. Usage stats is surely suggesting that internal customers find it VERY useful.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Aug 6 2021
Apr 1 2020
Oct 4 2019
This is a great question! I don't specialize in accessibility, so I also would love to hear input from someone with more experience in this field :)
Oct 2 2019
Will check with @osorio-juan-microsoft about whether screen reader would read this out...
Sep 18 2019
We did briefly discuss it in the TechCom meeting yesterday. Two issues have come up:
- The proposal in the task description is quite different from what has been implemented. For this to progress as an RFC, the task description has to be updated to reflect what we are actually deciding on.
Sep 12 2019
In T18691#5488544, @daniel wrote:In T18691#5488413, @CCicalese_WMF wrote:It seems that the design questions are resolved and the implementation is under review. Should the RFC be scheduled for discussion at TechCom?
We did briefly discuss it in the TechCom meeting yesterday. Two issues have come up:
- The proposal in the task description is quite different from what has been implemented. For this to progress as an RFC, the task description has to be updated to reflect what we are actually deciding on.
- We don't know if this is proposed purely as a third party feature, or for deployment on WMF systems. If it's just for 3rd parties, it may not even need an RFC, and could perhaps be done as an extension as well. If it's for WMF production, we will have to look very closely on the implications for caching and overall performance.
Jul 22 2019
@Aklapper You are right! Just did. Thanks for calling it out!
Mar 24 2019
Mar 6 2019
In T18691#5005766, @Esanders wrote:Preference: no, only <h2> to begin with
For shorter articles that don't have any/many h3's that might be fine, but for feature-article length pages it would be not very useful, for example if I wanted to share https://en.wikipedia.org/wiki/Barack_Obama#War_in_Iraq, a sizeable section, I would have to link to https://en.wikipedia.org/wiki/Barack_Obama#Presidency_(2009%E2%80%932017), which is several full pages away from the content.
Mar 5 2019
Thank you @alexhollender for sharing the amazing designs :)
Mar 2 2019
In T18691#4994519, @dbarratt wrote:Is it? Perhaps we should run a test on a high-traffic wiki and see which option is clicked more?
Mar 1 2019
In T18691#4991417, @dbarratt wrote:
Feb 28 2019
In T18691#4991150, @alexhollender wrote:
- Would it be beneficial to make this available without having to hover over the page title? I believe it would increase discoverability, decrease complexity of interaction, and minimize elements on the page jumping around.
Feb 12 2019
In T18691#4946400, @Tbayer wrote:In T18691#4933489, @Msftwikipmey wrote:@osorio-juan-microsoft and I work on a wiki that has a lot of traffic coming directly into sections instead of pages, so we are working on a design that will mitigate the issues mentioned in T18691#1098570.
[..]
I'm not a designer, but personally I think this looks like a promising approach. Thanks for sharing!
Out of professional curiosity: Are you planning to measure the impact of this change on users' reading/linking behaviour in any way?
In T18691#4937825, @Fomafix wrote:Please carefully test cases like:
[[File:Foo.png|thumb|left|Left floating object]] == Heading ==
Feb 7 2019
@osorio-juan-microsoft and I work on a wiki that has a lot of traffic coming directly into sections instead of pages, so we are working on a design that will mitigate the issues mentioned in T18691#1098570.
Nov 8 2018
Following the comments at T184619#4520676, we are going to create a pull request with a fix that removes the Google search form.