New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Resolve Safari Presentation Issues #137

Closed
toconnell opened this Issue Nov 18, 2016 · 2 comments

Comments

Projects
None yet
1 participant
@toconnell
Copy link
Owner

toconnell commented Nov 18, 2016

One of the goals for the milestone is to nail down all of these.

General:

  • topnav spans are not visible (does Safari implement z-index correctly?)
  • fixed pos top nav buttons are too close to the top

Dashboard:

  • accordion width jaggies
  • P width is out of controls on the System panel. Also affecting Chrome

Survivor Sheet:

  • top nav is missing
  • permanent affinities are huge
  • survivor avatar bottom margin is non-existent
  • right margin on hitbox inc/dec is non-existent

Campaign Summary view

  • top nav is missing
  • big pane floats aren't working correctly
  • retired accordion/clickable bottom margin is non-existent
  • settlement name is mysteriously centered
  • hunting party buttons are enormous
  • modal for managing the hunting party is ... not firing any wide selectors? How odd
  • fix right panel headings and fonts

@toconnell toconnell added this to the Survivor Sheet Refactor milestone Nov 18, 2016

@toconnell toconnell added the v1 label Nov 18, 2016

@toconnell toconnell removed this from the Black Friday - 2016 milestone Nov 27, 2016

@toconnell

This comment has been minimized.

Copy link
Owner

toconnell commented Nov 27, 2016

Moving this out of the Milestone. It's too much for now.

@toconnell

This comment has been minimized.

Copy link
Owner

toconnell commented Jan 23, 2017

There are a whole bunch of new presentation issues with Safari since the AR. I'm going to open another ticket for those.

@toconnell toconnell closed this Jan 23, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment