mirror of
https://github.com/cbracco/html5-test-page.git
synced 2025-08-21 05:11:45 +02:00
Compare commits
7 Commits
Author | SHA1 | Date | |
---|---|---|---|
|
3ce9efeb8e | ||
|
36e69fb5bc | ||
|
1602ce3a45 | ||
|
a73b6fef0b | ||
|
8a1c7b6906 | ||
|
7856bae2a3 | ||
|
557ee5c23b |
@@ -1,3 +1,11 @@
|
||||
# 0.2.1 (March 21, 2015)
|
||||
|
||||
- Fix duplicate IDs and formatting.
|
||||
|
||||
# 0.2.0 (April 8, 2014)
|
||||
|
||||
- add `<caption>` element to `<table>` examples.
|
||||
|
||||
# 0.1.0 (April 4, 2014)
|
||||
|
||||
- Initial release!
|
||||
|
114
CONTRIBUTING.md
Normal file
114
CONTRIBUTING.md
Normal file
@@ -0,0 +1,114 @@
|
||||
# Contributing to this project
|
||||
|
||||
*This information is heavily based on [this CONTRIBUTING.md document](https://github.com/necolas/normalize.css/edit/master/CONTRIBUTING.md).*
|
||||
|
||||
Before making a contribution, please take a moment to review this document. It will make the process easier and more enjoyable for everyone involved.
|
||||
|
||||
Following the guidelines in this document shows that you respect the time of the maintainers of this open-source project. In return, maintainers should show their respect for you by addressing your requests, issues, and contributions in a timely fashion.
|
||||
|
||||
## Submitting issues
|
||||
|
||||
GitHub’s built-in issue tracker is the preferred channel for bug reports, feature requests, and submitting pull requests.
|
||||
|
||||
**Do not** use the issue tracker for personal support questions. They will probably not be addressed.
|
||||
**Do not** derail or troll issues. Please try to keep things on topic and be respectful to others.
|
||||
|
||||
## Bug reports
|
||||
|
||||
*Demo or it didn’t happen.*
|
||||
|
||||
A bug is a problem that you can demonstrate to a maintainer on this open-source project. Good bug reports are very helpful, and encouraged!
|
||||
|
||||
If you are thinking about reporting a bug, please do the following:
|
||||
|
||||
1. **Search for existing issues** - it could have already been reported.
|
||||
2. **Check for fixes** - try to reproduce the bug using the latest release on the `master` branch in the repository.
|
||||
3. **If the bug persists**, submit an issue and create a live example of the bug using a public service like [jsFiddle](http://jsfiddle.net) or [Codepen](http://codepen.io). Link to your example in the issue that you submit.
|
||||
|
||||
Please be as detailed as possible. Ask yourself: What is your environment? What steps will reproduce the issue? What browser(s) and OS experience the problem? What would you expect to be the outcome?
|
||||
|
||||
## Feature requests
|
||||
|
||||
Feel free to request whatever you like, but please take a moment to think about whether your request is within the scope of the project. You should make a strong case for your request, otherwise the maintaining developers will probably not consider it. Provide as much detail as you can.
|
||||
|
||||
## Pull requests
|
||||
|
||||
Good pull requests are awesome. Bad pull requests are a headache. They should always be limited by the scope of the request, and avoid including unrelated commits.
|
||||
|
||||
**Please file an issue first** before deciding to do a lot of work. Otherwise, you run the risk of wasting time working on something that might not get merged into the project.
|
||||
|
||||
Follow this process if you’d like your work to be considered for inclusion in the project:
|
||||
|
||||
1. [Fork](http://help.github.com/fork-a-repo/) the project, clone your fork,
|
||||
and configure the remotes:
|
||||
|
||||
```bash
|
||||
# Clone your fork of the repo into the current directory
|
||||
git clone https://github.com/<your-username>/html5-test-page
|
||||
# Navigate to the newly cloned directory
|
||||
cd html5-test-page
|
||||
# Assign the original repo to a remote called "upstream"
|
||||
git remote add upstream https://github.com/cbracco/html5-test-page
|
||||
```
|
||||
|
||||
2. If you cloned a while ago, get the latest changes from upstream:
|
||||
|
||||
```bash
|
||||
git checkout master
|
||||
git pull upstream master
|
||||
```
|
||||
|
||||
3. **Never work directly on `master`**. Create a new topic branch (off the latest version of `master`) to contain your feature, change, or fix:
|
||||
|
||||
```bash
|
||||
git checkout -b <topic-branch-name>
|
||||
```
|
||||
|
||||
4. Commit your changes in logical chunks. Please adhere to these [git commit
|
||||
message conventions](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html)
|
||||
or your code is unlikely be merged into the main project. Use Git’s
|
||||
[interactive rebase](https://help.github.com/articles/interactive-rebase)
|
||||
feature to tidy up your commits before making them public.
|
||||
|
||||
Please add a test to the `test.html` file if appropriate, and test
|
||||
your change(s) in all supported browsers.
|
||||
|
||||
5. Locally rebase the upstream development branch into your topic branch:
|
||||
|
||||
```bash
|
||||
git pull --rebase upstream master
|
||||
```
|
||||
|
||||
6. Push your topic branch up to your fork:
|
||||
|
||||
```bash
|
||||
git push origin <topic-branch-name>
|
||||
```
|
||||
|
||||
10. [Open a Pull Request](https://help.github.com/articles/using-pull-requests/) with a clear title and description.
|
||||
|
||||
**IMPORTANT**: By submitting a patch, you agree to allow the project owner to
|
||||
license your work under the same license as that used by the project.
|
||||
|
||||
## Maintainers
|
||||
|
||||
If you have commit access, please follow this process for merging patches and
|
||||
cutting new releases.
|
||||
|
||||
### Accepting patches
|
||||
|
||||
1. Check that a patch is within the scope and philosophy of the project.
|
||||
2. Check that a patch has any necessary tests and a proper, descriptive commit
|
||||
message.
|
||||
3. Test the patch locally.
|
||||
4. Do not use GitHub’s merge button. Apply the patch to `master` locally
|
||||
(either via `git am` or by checking the whole branch out). Amend minor
|
||||
problems with the author’s original commit if necessary. Then push to GitHub.
|
||||
|
||||
### Releasing a new version
|
||||
|
||||
1. Include all new functional changes in the CHANGELOG.
|
||||
2. Use a dedicated commit to increment the version. The version needs to be added to the `README.md` and `CHANGELOG.md` (inc. date) files.
|
||||
3. The commit message must be of `v0.0.0` format.
|
||||
4. Create an annotated tag for the version: `git tag -m "v0.0.0" 0.0.0`.
|
||||
5. Push the changes and tags to GitHub: `git push --tags origin master`
|
@@ -1,4 +1,4 @@
|
||||
# HTML5 Test Page - 0.1.0
|
||||
# HTML5 Test Page
|
||||
|
||||
This is a test page filled with common HTML elements to be used to provide visual feedback whilst building CSS systems and frameworks.
|
||||
|
||||
@@ -28,4 +28,4 @@ HTML Test Page is licensed under the MIT Open Source license. For more informati
|
||||
|
||||
## Colophon
|
||||
|
||||
Made by [@cbracco](http://twitter.com/cbracco).
|
||||
Made by [@cbracco](http://cbracco.me).
|
||||
|
43
test.html
43
test.html
@@ -90,7 +90,7 @@
|
||||
<blockquote>
|
||||
<p>A block quotation (also known as a long quotation or extract) is a quotation in a written document, that is set off from the main text as a paragraph, or block of text.</p>
|
||||
<p>It is typically distinguished visually using indentation and a different typeface or smaller size quotation. It may or may not include a citation, usually placed at the bottom.</p>
|
||||
<cite><a href="#">Said no one, ever.</a></cite>
|
||||
<cite><a href="#!">Said no one, ever.</a></cite>
|
||||
</blockquote>
|
||||
</div>
|
||||
|
||||
@@ -205,8 +205,7 @@
|
||||
|
||||
<h2>Pre-formatted text</h2>
|
||||
|
||||
<pre>
|
||||
P R E F O R M A T T E D T E X T
|
||||
<pre>P R E F O R M A T T E D T E X T
|
||||
! " # $ % & ' ( ) * + , - . /
|
||||
0 1 2 3 4 5 6 7 8 9 : ; < = > ?
|
||||
@ A B C D E F G H I J K L M N O
|
||||
@@ -222,7 +221,7 @@ p q r s t u v w x y z { | } ~ </pre>
|
||||
<header><h1>Inline elements</h1></header>
|
||||
|
||||
<div>
|
||||
<p><a href="#">This is a text link</a>.</p>
|
||||
<p><a href="#!">This is a text link</a>.</p>
|
||||
|
||||
<p><strong>Strong is used to indicate strong importance.</strong></p>
|
||||
|
||||
@@ -327,40 +326,40 @@ p q r s t u v w x y z { | } ~ </pre>
|
||||
<legend>Text fields</legend>
|
||||
|
||||
<p>
|
||||
<label for="text">Text Input <abbr title="Required">*</abbr></label>
|
||||
<input id="text" type="text" placeholder="Text Input">
|
||||
<label for="input__text">Text Input <abbr title="Required">*</abbr></label>
|
||||
<input id="input__text" type="text" placeholder="Text Input">
|
||||
</p>
|
||||
<p>
|
||||
<label for="password">Password</label>
|
||||
<input id="password" type="password" placeholder="Type your Password">
|
||||
<label for="input__password">Password</label>
|
||||
<input id="input__password" type="password" placeholder="Type your Password">
|
||||
</p>
|
||||
<p>
|
||||
<label for="webaddress">Web Address</label>
|
||||
<input id="webaddress" type="url" placeholder="http://yoursite.com">
|
||||
<label for="input__webaddress">Web Address</label>
|
||||
<input id="input__webaddress" type="url" placeholder="http://yoursite.com">
|
||||
</p>
|
||||
<p>
|
||||
<label for="emailaddress">Email Address</label>
|
||||
<input id="emailaddress" type="email" placeholder="name@email.com">
|
||||
<label for="input__emailaddress">Email Address</label>
|
||||
<input id="input__emailaddress" type="email" placeholder="name@email.com">
|
||||
</p>
|
||||
<p>
|
||||
<label for="search">Search</label>
|
||||
<input id="search" type="search" placeholder="Enter Search Term">
|
||||
<label for="input__search">Search</label>
|
||||
<input id="input__search" type="search" placeholder="Enter Search Term">
|
||||
</p>
|
||||
<p>
|
||||
<label for="text">Number Input <abbr title="Required">*</abbr></label>
|
||||
<input id="text" type="number" placeholder="Enter a Number" pattern="[0-9]*">
|
||||
<label for="input__text2">Number Input <abbr title="Required">*</abbr></label>
|
||||
<input id="input__text2" type="number" placeholder="Enter a Number" pattern="[0-9]*">
|
||||
</p>
|
||||
<p>
|
||||
<label for="textarea">Textarea</label>
|
||||
<textarea id="textarea" rows="8" cols="48" placeholder="Enter your message here"></textarea>
|
||||
<label for="input__textarea">Textarea</label>
|
||||
<textarea id="input__textarea" rows="8" cols="48" placeholder="Enter your message here"></textarea>
|
||||
</p>
|
||||
<p>
|
||||
<label class="error">Error</label>
|
||||
<input class="is-error" type="text" placeholder="Text Input">
|
||||
<label for="input__text3" class="error">Error</label>
|
||||
<input id="input__text3" class="is-error" type="text" placeholder="Text Input">
|
||||
</p>
|
||||
<p>
|
||||
<label class="valid">Valid</label>
|
||||
<input class="is-valid" type="text" placeholder="Text Input">
|
||||
<label for="input__text4" class="valid">Valid</label>
|
||||
<input id="input__text4" class="is-valid" type="text" placeholder="Text Input">
|
||||
</p>
|
||||
</fieldset>
|
||||
|
||||
|
Reference in New Issue
Block a user