joexn/legacycss

Legacy CSS - Modern and Lightweight CSS Framework

legacycss's Issues

Menu animation (4.0 beta)

As you can see, the text is visible when the background is not for a short time during the animation.

This issue is present across all browsers.

Issue with page spacing.

Navbar producing blank space between divs

This issue is due to the .nav class being displayed as an inline-block which should be block.

SASS CSS3

Is this project planning on moving to the CSS3 version of SASS?

message box font colour

When using

<div class="message">Content</div>

the class doesn't seem to contain a color attribute, as seen here.

There needs to be a color: #FFF here.

This will be added in the next development preview.

Legacy Reset Issue

For some reason, in the Legacy Reset <sup> is reset so it's basically useless.

Include readable source

Include a readable, formatted source CSS (or SCSS, etc.) file, in addition to the minified version, to make editing easier.

Inputs don't look like inputs

There's no way for a user to know without clicking that this is an input field.

Include build instructions

Include instructions in the README for how to compile from SASS to formatted CSS, and how the minify the CSS. Something like this:

Install the SASS CLI if you haven't already:

$ npm i -g sass

To compile from SASS to CSS, do the following:

$ sass legacy.sass legacy.css

Or to compile a minified file for production:

$ sass -t compressed legacy.sass legacy.min.css

Will Legacy ever be stable?

The first release of Legacy, 1.9, was on April 9. Today, less than three months later, we're on Legacy 4.1, and plans for Legacy 5 have already been mentioned. Every major release so far has been a complete rewrite. Will Legacy ever become stable? It's hard to become invested in a project if it's being rewritten from the ground up literally every month.

Re-writing the .btn classes

Unfortunately at the moment, I do not have enough time to fully work on Legacy. I was hoping someone could help me simplify a piece of code.

All of this code is to long, and some of it is repetitive.

Any help would be greatly appreciated!

Legacy 3 Navbar Overlay Issue

Recent implementation of a new navigation bar has been successful but there is a slight problem with overlaying different elements.

The link has been removed due to the dev preview has ended.

development versions of legacy

Want to test Legacy before anyone else? Email me to request access to our slack. Beta releases are distributed there.

Navbar Issues

• Navbar item margins not working correctly.
• Navbar items on right float not aligning properly.
• Navbar not scaling on smaller displays.

Legacy 4.3 and changes.

So, Legacy 4.3 is coming out on the 25th of April 2017 - but there are going to be some changes, firstly, the domain name is changing and that will be announced closer to the 4.3 release. The name is also changing from Legacy Framework to Legacy CSS due to some conflicting issues with something with a similar name. Over the next month these changes are going to be made and the transition will be super smooth.

Got any questions or ideas? Drop me an email.

See you soon!

Legacy 2 SASS Development

I am going to keep this issue open and I will keep it updated with news on the SASS version during development.
I have had encouraging results with testing the SASS version so far, although there are a lot of issues I want to fix before the Legacy 2 release.
http://i.imgur.com/bywRreR.jpg

@nloveladyallen
@nishad

Input for passwords not styled

Issue title explains all.

Requires input[type=password] be added to the end of line 1 in 'legacyforms.sass'.

Navbar overlay issue

There is a bug with the new pure css navigation bar set to be in Legacy 3. The issue is that it overlays anything else and isn't fixed.

The issue can be fixed by adding:

body {
  top: 56px;
}

but if you don't use the navigation bar then this will push everything else down.
Legacy 3 will not be released until this bug is fixed.

push pull

I would like to see a push / pull class like in Skeleton, really missing it (didn't use LegacyCSS yety so maybe I missed someting studying it) like LegacyCSS so far.

Navbar dropdown not aligning.

Legacy for Phones and Tablets

Better phone and tablet support is coming in Legacy 4.

[QUESTION] Sass or LESS files ?

Nice work, appreciate it, It is good to have a simple css framework.
Is there plans to release any CSS preprocessor support ? I'm really looking into that option.

Menu font-size

As seen here: the menu font size changes when menu is extended. I know what the issue is, I'll fix it tomorrow.

Examples

I've opened PR #6 to add an example, but more examples should still be added.

Make all `code` monospace

Currently only code.pretty is monospace, and plain code is in sans-serif. All code should be monospace. There is no context in which have code be proportional makes sense.

Read this before reporting an issue!

Please read this quick blog post about opening issues

Use of Product Sans

Google's Product Sans font isn't open source - see their license. Although it looks great, I would recommend swapping it out for a font like Open Sans or Roboto to maintain open source status.

Fonts not sizing correctly.

It seems like fonts are sizing properly on smaller displays.
This issue should be fixed in the next update.

hero font colour issue

when the style hero default is being used, the font color is coming back as the same as the background color.

<div class="hero default"><h1>Test</h1></div>

try this out by heading over to here and try changing the hero to default.

I've already found the problem and it will be fixed in the next release.

Cross Browser Transitions Test Failed

The transitions on different browsers have failed. This will take a few minutes to fix but is legacy-wide.

Dropdown icon misaligned on Windows

Here's the dropdown in Firefox on Windows:

And for reference, Firefox on OS X:

This is not an issue with Helvetica Neue vs. Roboto. Manually changing the font to Roboto on OS X does not reproduce the issue.

I don't know if there's a way to fix the issue or if we'll have to find another icon for the dropdown that works cross-platform.

Support for SCSS

In the Legacy 3 release, coming very soon, I am expanding support to include SCSS and LESS and further developing the SASS version to include width and page variables.

There will be a development preview of these features.

Replace JavaScript menu system with pure CSS

Similar to the CSS, it would be great to see a formatted, readable, commented JavaScript file in addition to the minified file.

I'm also curious to know what the JavaScript does: what justifies its inclusion in a self-proclaimed "lightweight, simple and modern UI framework"?

hero font size is set to 50px

the font size for the hero is set to 50px

.hero
  position: relative
  background-color: #FFF
  text-align: center
  color: $legacy
  font-family: $font
  padding: 10rem 0
  margin-bottom: 5rem
  h1,h2,h3,h4,h5,h6,p
    line-height: 1.3
    color: $legacy
    font-size: 50px

this will be fixed soon.

Google Analytics disabling navigation bar.

There is currently a bug in Dev Preview 3 that when Google Analytics code is placed inside the website, the navigation bar does not scale to small devices

input button font issue

In the latest development release of legacy (Dev Preview 1),

<input type="button" value="Test">

the font and text-transform is set incorrectly.

This will be fixed in the next dev release.

New look for cards (a new element?😉)

I am currently away from my PC so i cant work on Legacy. This issue is to remind me on what i need to work on when i get back.

Check milestones for info on Legacy releases.

.hidden-on-desktop not demoed in legacy-framework.com/docs

Should show both "This button will be hidden on tablets" and "This button will be hidden on desktops"

Tester Needed

I am around half way through the development of Legacy 4 and there is an issue I need someone to debug. It has something to do with the framework and I can't seem to fix it.

Many thanks,
Joe.

Modal window issue

In Firefox, the modal window appears for a split-second on initial page load before disappearing. In all other browsers, it is hidden immediately.

Inputs other than text

Support for non-text inputs needs to be significantly improved. All checkboxes are hidden by default, radio buttons take up 50% width, etc. That's not to mention they aren't styled at all.

Legacy 4.2 is in development

This issue will remain open and contain information on the next planned release until it is released.

There are some issues with 4.1 that need to be fixed but this updated will be a minor update as there are some changes to the core of the framework.

Please look out for issues with the Legacy 4.1 tag. These will be fixed in 4.2.

New issue styling
From 4.1 onwards, when creating an issue please be as detailed as possible, if you know the fix, mention it and if possible, link to the file where the issue is or will be fixed.

Head's up!
The dev branch will be updated with the latest work, everything is still in development and being worked on in the dev branch so no issues please. When the beta is released, then you can open issues and pull requests.

---

August 12^th - Legacy 4.2 development has started.

Column separators on mobile

These are unusably small:

I suggest something like how Bootstrap does it (and I believe earlier versions of Legacy):

Close submenu on mobile

There's no way to close a submenu on mobile:

Input buttons have an outline when clicked

This is a minor issue as it only requires outline: 0 to be added to to the end of this class.

Tables on mobile

Should probably scroll sideways instead of overflowing. (Subjective)

No Navbar Button - Completely broken.

So I was looking through the navbar, seeing if I could fix some issues when I tested the navbar in Legacy 3.1 and nothing. No menu button, at all. So I went back to the dev preview and nope, not working there either. This is a major bug that I can't seem to get my head around. Any help will be amazing. I will focus more on this when I finish my exams (2 weeks!)

As you can see.. No navbar button.

This was 100% working before.

[Announcement] Legacy 3

Hello!,

Legacy 3 was released today. There are some things I still want to do but my exams aren't over until June 27th. The wait was to long, so I decided to fix all the bugs and add some new features and here we are.. Legacy 3.0.

Legacy 3.1 is already in development and will add more small features and whatnot.

Until then, thanks for helping with Legacy.

Thanks,
Joe.

The blog is back

Legacy 4 is now in full development and it's coming together quite nicely. If you are wondering where is the 'dev' branch. I cover that in a blog post at: https://blog.joexn.com/posts/removing-the-dev-branch

---

Check back at the blog for more updates on Legacy.

legacy-framework.com has no menu on mobile

It still uses the old Font Awesome classes, instead of the new CSS classes.