* prints first error message only
* update signup error messages, missing password not working (wip)
* remove alerts, show notEmpty, first error only per param, update unit test
* move changes to client side
As reported in #10502, adding a 1 pixel right margin to *all* nodes with
the member-stats class will affect the display when you click on the
avatar as well, which will then break the layout because of that
additional margin.
Instead of adding the margin to .member-stats in general, let's just add
it to the condensed version so that it really just addresses the
flickering on Chrome/Chromium as reported in #10379.
I've tested whether the flickering still happens via a small
xdotool-loop (just to make sure I don't get too shaky with the mouse):
for i in $(seq 500 508); do xdotool mousemove "$i" 250; sleep 5; done
The flickering doesn't happen anymore and the layout in the party
members overview and the stats overview when you click on the avatar is
no longer distorted.
Signed-off-by: aszlig <aszlig@nix.build>
Fixes: #10502
* Turning H2s into anchors to add hand cursor and to create addressable page fragments
adding ref to target individual entries
adding scroll handler to make sure expanded result is in view.
* combining click handler directives as per CR
* changing question display to always render, then hide via CSS, vs only render when state changes.
* updating pug template to include heading in each URL fragment
* simplifying logic & moving to vue-bootstrap accordion since multiple open panels is not required
* adding pointer cursor to FAQ headings
* moving initial hash checking to data prop instead of mounted so it does not trigger oddities on on hash change (re-mount)
* using new pug HTML for bootstrap collapse
* removing extraneous markup
* updating styling to match existing page
* removing fancier than necessary markup, and attendant styles
* using more standard event property
* Added session check before route changes, but express isn't finding route
* Added a logout component. Changed route to logout on server. Typing 'logout' in URL will logout of Vue + Express
* Removed commented text from previous version
* Updated logout function to comply with formatting and eliminate unused blocks
* Added package-lock.json back
* package-lock.json
* recreated package-lock file
* fix(auth): allow logout from direct visit to /logout path
* fix(merge): clean up more misc changes
* fix(merge): remove extra file
* added 1px margin-right to .member-stats
* added unit test for flicker prevention style
* remove .only() from unit test
* rewrote margin test using computed style
* Remove outdated server readme
* Open correct group modal from header
* Update party button after joining party
* Review: fix invite members not working without reload
* Remove invite-modal from group page to prevent duplicates
* Pass correct group to invite modal
* removing the 24px top margin on .modal-dialog .title so boss HP and difficulty line up
* stop overloading title so much and use a properly-scoped style
* removing unnecessary temp vars
* using SCSS color vars as per CR
* using relative font size measurements instead of absolute pixels, and adding popover override CSS to not break quest shop & invite notifications
* removing redundant font declarations
Added a 'habitica:update-challenge' call to mirror the 'clone-challenge' call. This properly sets the 'cloning' flag and makes things more consistent.
This fixes the a bug related to #10419 described in the #10419 thread
* added responsive scss to allow modals to respond to changing window size
* Remove unecessary space
* moved scss around
* remove unnecessary space
* Adjust left and right panels to be more responsive + moved css for buyQuestModal into its respective vue file (startQuestModal css wasn't working in its vue file... I can't figure out why)
* removed important to get rid of extra scrollbar
* moved css all to one file
Whenever one is hovering an item from another user, the bonuses of these
items are shown for the own user. So for example if you're a mage and
view a Royal Magus Robe of another mage, the class bonus is 6.
However if you're a warrior, the class bonus displays as 0 because the
attributes grid is always using the stats for the own user even if
viewing equipment of a different user.
I've fixed this by moving the user object to the properties in
attributesGrid and passing the current user from every other Vue file
that's using attributesGrid.
Not sure whether this is the right approach, as I'm no expert in Vue.js
but some testing with the client now shows the correct values.
Signed-off-by: aszlig <aszlig@nix.build>
Matteo Pagliazzi