Fri, Feb 16
If AH team is going to be working on this, I wouldn't mind doing the design. I can put up potential solutions soon.
Thu, Feb 15
yeah we can move this to needs sign off. looks good to me, i can resolve it.
yes, happens on same article on safari as well
If I recall correctly I noticed it was related to unclosed div's in the article HTML.
Wed, Feb 14
much better :)
Tue, Feb 13
or robot uprising
good point. let's use automated accounts
Fri, Feb 9
we also have a page for the more in-depth descriptions (no reference to the phab ticket necessary unless people are curious
Do you think anything extra is necessary?
How long will that feedback link be present?
when I put the link, I was thinking of it as a permanent way of providing feedback on Beta features.
@Tgr my bad, I used something that's an upcoming addition to OOUI iconset. design team is working on upgrading the iconset.
Thu, Feb 8
I would recommending hiding the justification for captcha. it is a commonly used feature to prevent bots. the user expectation there is pretty much set and known. we can link out to "learn more"
Wed, Feb 7
@Baloch007 I laid the production logo with the mockup you provided and it matches
Tue, Feb 6
oh cool! thanks!
the AC says link feedback button to https://www.mediawiki.org/wiki/Reading/Web/Settings
Mon, Feb 5
hey @Tgr thank you for informing design about this change.
Thu, Feb 1
blue shadow is the focus ring, we need it. not problematic from design POV
can we update the hamburger menu icon to the latest one from our iconset?
I think we need to keep this open. T143535 is made up bunch of other things, as well. but the end goal is to improve top of the article experience
Tue, Jan 30
Mon, Jan 22
Specialpages branch also has minor impact  on other pages. not sure if we want to test these as the change is very minor but good to have a record of it. I have checked the following special pages and they work as expected
Fri, Jan 19
@Baloch007 can you verify this SVG to make sure there aren't any script issues?
@Baloch007 I think the script problem is imp and we should fix it... but we have limitation on the size
I thought we had reviewed the earlier SVG before we deployed. let me update it in description
Jan 18 2018
Looks good to me! thanks @Jdlrobson
Jan 17 2018
Screenshots look good to me.
Jan 16 2018
I just tried these steps on reading staging. The settings don't get reverted for me. they do get saved even with back button but you have to refresh the page to see the change take effect.
they can be smaller, that was kinda intended
Jan 10 2018
@Baloch007 can you verify if the logo is correct in the SVG?
over to you @Jdlrobson
Jan 9 2018
Looks good! What happened to "expand all sections" though?
Jan 7 2018
Jan 5 2018
Jan 4 2018
is this still blocked?
Jan 3 2018
https://phabricator.wikimedia.org/T182362 < this is still a blocker for deploying this branch
It doesn't look like the mock provided but works for now
Jan 2 2018
this is breaking default table styles for all infoxes on staging
Let's remove this option from tablets for now. no change in the label.
Dec 21 2017
Tested on beta cluster
as per @pmiazga created a subtask to this for the above issue -
The delay is making the experience much better. I can toggle the switch now. looks good.
Overall settings work seems to be working as expected! yay!
Dec 20 2017
NOTE: This doesn't account for the two "views" of the Watchlist. Please update screenshot/provide a mock.
Dec 19 2017
Legal aspect ratio is closest to most devices. it comes close to common screen sizes than A4 or letter
Dec 15 2017
just spoke with @pmiazga about 3 points
It's safer to use the mobile html (including the transforms) to create the PDF. I would also like to know how this decision affects the estimated amount of work
can we use the same one with a different text?
Dec 14 2017
I'm okay showing the same empty preview for 500 errors as well
then the existing spacing needs to be fixed.
zpl.io/bAOdAPx < this was the spec provided for it and If i remember correctly the spacing was correct? was there a change that broke the spacing?
Dec 13 2017
I stumbled on Marina Abramovic's article on en.m., and I thought "Page issues" was some kind of vandalized Wikidata description.
Dec 9 2017
If something is in beta but is configurable we still want to list it, correct?
Dec 8 2017
can we just show/hide the lock>checkmark based on the toggle and save the preference async?
the distinction would only appear on talk namespaces?
based on reading-web-stage
after trying for an hour, I think I found the regression and fix for this!
I tried a bunch of ways to break the table in print mode as well as all the @page props but none of it works. tried zoom and transforms as well. there has to be a way we break up the table instead of scaling the entire article. the description has possible 2 options but @ovasileva we should explore a third option. breaking tables somehow.
Dec 5 2017
Oh sorry, I missed this comment. I would want to see the FOUC we are talking about. I should have checked it before when toggleswitches were deployed.
Thanks @Kaartic for reporting the issue!
@Tbayer https://phabricator.wikimedia.org/T182059 just for references, cases like these are only user reported. in this case, some browser is claiming to be chrome. if we have a proper funnel, we can spot these issues
Just FYI this is now fixed on my testing device. I had this issue earlier but since we deployed the spinner, everything works fluently.
t's not clear how we show the other features that are in beta e.g. back to top, categories, lazy loaded references, wikidata descriptions. What is the plan with these?
can we deploy it on staging? I'm seeing checkboxes right now.
let it be center aligned for now
@Jdlrobson yes can be merged
Just figured the font size for the feature title is wrong
When in stable and opting into beta, you need to refresh page to see the other options. Is this something we want to fix?
yeah I was going to surface this as well. let me answer this on T67079 we need to reflect the changes right away. right now the state is in flux.