Seems fixed now. Thanks :3
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Fri, Apr 25
Ok, I'll improve it, because I still have a lot to learn about Phorge and its source code, otherwise I'll fix those issues myself
If there is an issue in Phorge then please provide steps to reproduce in Phorge. Please also strip unneeded full quotes which make comments hard to read. Thanks!
In T15056#21737, @danielyepezgarces wrote:T391929 In that task on Wikimedia Phabricator, I had put some issues
Steps to reproduce the bug:
- Enable the "Dark Mode (Experimental)" theme in Wikimedia Phabricator.
- Go to the Phabricator Workboard.
- Click on any button that has a dropdown menu.
And with these steps you can see the error like the images I have attached
I just checked that the issue can be replicated in the Accessibility workboard, on the Affects-Wikimedia workboard it looks good
In T15056#21750, @aklapper wrote:In T15056#21737, @danielyepezgarces wrote:@danielyepezgarces: Please always provide clear steps to reproduce something somewhere, in most recent Phorge itself.
Thu, Apr 24
In T16035#21703, @aklapper wrote:but the "Regular" Icon Style is not available in the free version and is "Pro only".
I was wrong or misinterpreted. fa-regular-400 as part of the "Free" version exists at https://github.com/FortAwesome/Font-Awesome/tree/6.x/webfonts
git rebase master
Remove two orphan CSS rules from phui-timeline-view.css
git rebase master only; still Needs Revision
In D25911#25886, @valerio.bozzolan wrote:Small question: if an user migrates from gmail.com "less secure apps" to gmail.com "App Passwords", isn't that the very same thing?
Tested on a fresh install!
Seems good to make D25503 more complete, thanks!
Small question: if an user migrates from gmail.com "less secure apps" to gmail.com "App Passwords", isn't that the very same thing?
Good news: we can be even more aggressive about that broken CSS rule, since it seems orphan.
git rebase master
Wed, Apr 23
implement documentation tips - thanks - also re-wrap some lines to be under 80 chars
P.S. I wonder... what happens if we expose the width/height here. But probably just touching that would be enough. Still, patch welcome 👍
Thanks. Yes. I can reproduce. Relevant documentation:
Thaanks @20after4 - I would say: be bold and mark as resolved to get eternal glory 👍 half year of discussion is probably enough and everybody seems happy about this.
Hi @mainframe98 - I still see your block. Do you like the new documentation now? 👍
Tue, Apr 22
This project is now abandonware without you. 😆
Gents, you’re both nothing short of geniuses
Gents, you’re both nothing short of geniuses—fixed before I’d even blinked! Thanks. Will look at fixing it permanently in T15513.
Fix was reverted for now as it had bad side effects.