1.1.0 #21
Merged
1.1.0 #21
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Added feature which will allow `single-page-express` to remember the scroll position of pages that have been visited. It will also remember the scroll position of child containers on each page as well, but only if those containers have assigned `id` attributes. - Added `alwaysScrollTop` param which will let you disable this behavior app wide and `res.resetScroll` which will let you disable this behavior on a per-route basis. - Added new behaviors to the default render method. It will now: - Update the attributes of the `<html>` and `<head>` tags. - Add new children to the `<head>` tag if anything new is in the template render. - Delay the DOM update until any new `<link>` or `<script>` tags load to prevent a FOUC. - Set browser focus appropriately after the DOM update. Also added `res.focus` to let you set it manually. - Announce page changes to screen readers. - Added `res` properties which will let you remove elements from the `<head>` tag on a per route basis: `res.removeMetaTags`, `res.removeStyleTags`, `res.removeLinkTags`, `res.removeScriptTags`, `res.removeBaseTags`, `res.removeTemplateTags`. There is also `res.removeHeadTags` to remove all children of the `<head>` tag except the `<title>` tag. - Added `topBarRoutes` param to allow restricting the top bar to certain routes. - Added `req.singlePageExpress` which you can use to detect if your route is executing in the `single-page-express` context. - Fixed a bug which caused back/forward buttons to not function properly sometimes. - Fixed a bug which would cause the top bar not to ever hide if it was enabled but the default render method was replaced. - Fixed a bug in the Express sample app that would cause server-rendering to fail on routes with more than one `/`. - Added a new sample app. - Added an automated test suite and a few starter tests. - Refactored some code to simplify it. - Removed some unneeded dependencies. - Updated dependencies.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
single-page-expressto remember the scroll position of pages that have been visited. It will also remember the scroll position of child containers on each page as well, but only if those containers have assignedidattributes.alwaysScrollTopparam which will let you disable this behavior app wide andres.resetScrollwhich will let you disable this behavior on a per-route basis.<html>and<head>tags.<head>tag if anything new is in the template render.<link>or<script>tags load to prevent a FOUC.res.focusto let you set it manually.resproperties which will let you remove elements from the<head>tag on a per route basis:res.removeMetaTags,res.removeStyleTags,res.removeLinkTags,res.removeScriptTags,res.removeBaseTags,res.removeTemplateTags. There is alsores.removeHeadTagsto remove all children of the<head>tag except the<title>tag.topBarRoutesparam to allow restricting the top bar to certain routes.req.singlePageExpresswhich you can use to detect if your route is executing in thesingle-page-expresscontext./.