Skip to content

Conversation

if (rawPursuance !== undefined) {
return rawPursuance.name;
} else {
return "Jump to a pursuance";
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

return "Jump to a " + PROJECT;, please

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See 136c571

pursuances[currentPursuanceId] : "";
return (
<div className="content about">
<h1>About This Pursuance</h1>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

About This {PROJECT_CAPITAL}

@4xdk
Copy link
Collaborator Author

4xdk commented Jan 6, 2019

Done and done :)

@4xdk
Copy link
Collaborator Author

4xdk commented Jan 6, 2019

Added some CSS fixes for project selection dropdown on tablet (hidden between 768px and 960px) and in mobile menu

@elimisteve
Copy link
Member

screenshot-effective-cssbug-topnavdoubled-768to1200-screenshot_2019-01-06_16-31-53

@4xdk How about hiding the new project switcher dropdown between screen widths 768px and 1199px?

@4xdk
Copy link
Collaborator Author

4xdk commented Jan 7, 2019

Could just set a max width for the dropdown element too ... I'll have a look

@elimisteve
Copy link
Member

Could just set a max width for the dropdown element too ... I'll have a look

@4xdk That's true, though then someone could join a project with a long name and have the switcher disappear on the device they're using, which is kind of weird... though I guess always hiding it for that screen size just in case they join a project with a long time would kind of suck.

Ah, maybe setting a max-width for the name of the project as visible at the top of the switcher (but allowing the name to take up multiple lines once the drop-down is expanded) and doing overflow-x: ellipsis makes sense?

@4xdk
Copy link
Collaborator Author

4xdk commented Jan 7, 2019

Yeah, was thinking about the second option. Good idea about multiple lines in the dropdown itself, shouldn't be a problem.

@elimisteve
Copy link
Member

@4xdk 👍

@4xdk
Copy link
Collaborator Author

4xdk commented Jan 26, 2019

Should be good now @elimisteve

@4xdk
Copy link
Collaborator Author

4xdk commented Feb 24, 2019

Re. the conflict: just keep both changes one after another.

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

Labels

None yet

2 participants