| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
I like it! The way it shows IV's is much better like this. |
Sorry, something went wrong.
|
I like this, minimal and easier to read, how would it account for the recent PR #2475 (adding gen info to marker labels), possibly next to level? |
Sorry, something went wrong.
There was a problem hiding this comment.
Increase top margin on the link for the coordinates. People on mobile + fat fingers = accidents.
Sorry, something went wrong.
|
@daangroot add margin-top: 5px; to the # nav part to make the changes @sebastienvercammen suggested for fat fingers. |
Sorry, something went wrong.
|
@sebastiaanvercammen I don't see why a top margin would help. There is nothing above it that could be pressed, so nothing can go wrong. |
Sorry, something went wrong.
|
@daangroot u could press something like exclude or notify for e.g. |
Sorry, something went wrong.
|
Oh yes sorry, did not think about the no iv label. |
Sorry, something went wrong.
|
I added a 5px top margin to the navigate class as suggested. |
Sorry, something went wrong.
| } | ||
|
|
||
| &.navigate { | ||
| position: absolute; |
There was a problem hiding this comment.
why do we need that? im not a fan of position: absolute.
Sorry, something went wrong.
There was a problem hiding this comment.
That's how it was done before. It can be done differently but this is the easiest way.
Sorry, something went wrong.
| height: 48px; | ||
| width: 48px; | ||
| margin-bottom: 11px; | ||
| margin-bottom: 15px; |
There was a problem hiding this comment.
Is there a reason why we would have to increase it?
Also, can u provide a screenshot with the difference compared to my simple change?
Sorry, something went wrong.
Sorry, something went wrong.
|
You should consider leaving the ADS labels on the IVs to eliminate confusion. Many (not all) tools use ADS, but the in-game appraisal uses SAD. |
Sorry, something went wrong.
|
@dripdropper I removed them because it looked better, but I can understand that it might cause confusion, so I will add them back. |
Sorry, something went wrong.
|
nice changes, looks neat and triggers no warning or epileptic episodes |
Sorry, something went wrong.
|
Werks Gud. Thanks for your efforts. |
Sorry, something went wrong.
|
Thanks. It works perfect 👍. |
Sorry, something went wrong.
There was a problem hiding this comment.
👍 good work
Sorry, something went wrong.
|
Looks good and works. |
Sorry, something went wrong.
There was a problem hiding this comment.
Final change, rest looks OK. 👍
Sorry, something went wrong.
|
|
||
| function getTypeSpan(type) { | ||
| return `<span style='padding: 2px 5px; text-transform: uppercase; color: white; margin-right: 2px; border-radius: 4px; font-size: 0.6em; vertical-align: middle; background-color: ${type['color']}'>${type['type']}</span>` | ||
| return `<span style='padding: 2px 5px; text-transform: uppercase; color: white; margin-right: 2px; border-radius: 4px; font-size: 0.75em; vertical-align: middle; background-color: ${type['color']}'>${type['type']}</span>` |
There was a problem hiding this comment.
Move all the inline CSS to the stylesheet, and remove the getTypeSpan function. Since the HTML will be much shorter, it'll be clearer if it's no longer a separate function.
Sorry, something went wrong.
Sorry, something went wrong.
There was a problem hiding this comment.
RE: Discord:
[11:57 PM] Konturka: There is a small issue though. The type is not centered inside its box on some mobile browsers.
[11:58 PM] Konturka: This was already an issue but it was less noticeable because the font size was smaller.(edited)
[12:00 AM] Konturka: On chrome and samsungs browser it's not centered.
[12:00 AM] Konturka: On firefox it is.
Sorry, something went wrong.
|
Looking at the Type box code and testing locally |
Sorry, something went wrong.
|
Adding padding-top: 0.45em (or padding-top:2.25%) on the .type element fixes it for mobile browsers but breaks on desktop. this could probably be fixed by adding the necessary overrides to mobile.scss |
Sorry, something went wrong.
|
@sebastienvercammen I've tried a lot of things to make the type text centered, but I couldn't fix it. |
Sorry, something went wrong.
|
Maybe we can merge it and fix it afterwards. I can make an issue for this problem, so other people are aware of it and can maybe fix it. |
Sorry, something went wrong.
|
@daangroot We won't merge without the fix. The PR is instead tagged as "help wanted". |
Sorry, something went wrong.
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Description
Small improvement of style and formatting of the Pokémon marker label.
See screenshots below for the changes made.
Motivation and Context
I did not really like the look of the label, so I thought lets make it more beautiful :)
How Has This Been Tested?
Tested on my main setup.
Screenshots (if appropriate):
Old:

New:

Types of changes
Checklist: