-
Notifications
You must be signed in to change notification settings - Fork 975
Improve typography in Brave Payments notification panel #12770
Comments
Hey guys, is this still available - would love to take a stab at this :) |
@arsalankhalid We'd love your help! Go for it... cc @NejcZdovc |
@arsalankhalid yes it's still available. If you need any help let me know. Thank you |
Great, thanks for passing it over - will reach out :) |
@NejcZdovc hard to re-create this, what are your thoughts? Is this fixed/non-existent, or an edge case based on specific messages the user received, just as the million dollar give away example, how can I re-create that? |
@arsalankhalid try starting your run with |
Great thanks, let me give that a shot. |
Sorry for the radio silence, been a bit busy. Will take a stab tomorrow I more than hope :) |
Hey still not sure how to re-create, how exactly do i 'claim' a promo? |
Sadly don't see it when I run it, even in staging :( I was hoping there was a way to test running the promos, or not possible? It would be easier to ensure the typography is good for all types of promo messages...as long as those promos are actually fake :P It's also possible i tried to run the promo already, in staging - but not sure. Please advise |
You can use this profile. Just copy it into user profile folder and run |
I hate to be the local noob, but wheres our user profile? Trying to find Brave directory on OSX. Almost seems like a feature for users to easily switch their profiles through preferences/settings? I saw some open and closed tasks regarding to 'portable profiles', but don't see anything in preferences to easily switch. Also that archive.zip file looks sketchy at first look lol, but i guess its a profile :P |
your user profile is in |
@arsalankhalid if you have time we can jump on a call and check it out. Just send me an email to |
#12770 - Improved styling on promotion component
Test plan
LEDGER_ENVIRONMENT=staging
Original issue description
Sub-text issues to improve:
Current:
Improvements:
The text was updated successfully, but these errors were encountered: