Priority

Perspective

Callback to run before any render pass (see davidsums popup discussion)
- up:render:prepare or up:render:setup or up:render:options
- Would we rename up:fragment events to get pressure off the up:fragment namespace?
  - up:render:load
  - up:render:loaded
  - up:render:keep :(
  - up:render:offline
  - up:render:inserted :(
  - up:render:hungry :(
  - This would leave up:fragment:poll
Consider a callback to manipulate render options before interactive element
- Either element-specific ([up-on-follow], [up-on-submit], etc.)
- Or generic ([up-on-use="..."], [up-setup="..."], [up-before], [up-guard], [up-on-run] [up-on-activate="..."], [up-on-start])
  - Use is short, but conflicts with [up-use-data] and does not work for polling
Open overlays from template selectors
Support X-Up-Open-Layer: { type, ...VISUAL_OPTIONS }
- Works for both success and failed response. There is no X-Up-Fail-Layer option.
- Ensure that X-Up-Target also works for both success and failed response. There is no X-Up-Fail-Target header in the response.
- Support unpoly-rails (up.layer.open())
- Recommend to also set X-Up-Target
FM required overriding of history from the server
- They really wanted { navigate }, no?
  - But can we really change navigation options at that point?
Remove params parsing for up.watch(), support formdata, ElementInternals
- We can just parse the entire form with new FormData(), then filter on contained elements
  - We will still need to know form fields for that
- Replace up.Params.fromForm() with new this(new FormData(form))
Consider [up-zone] as an origin-aware lookup without further logic
- Also support :zone as a new pseudo
  - Layer priority beats zone priority
- config.zoneSelectors = ['[up-zone]', ':main]
- config.noZoneSelectors = ['[up-zone=false]']
- I think without an { origin } we only want to check out :main. Maybe it's not configurable?
- Do we want to allow [up-zone="name"] (and include it in targetDerivers), or should it be [up-zone][id="foo"]?
  - If we want to get rid of [up-href] (to enable morphing), we should encourage the use of IDs
- If we want to mount arbitrary pages to mount in an [up-zone] it should be a parent.
  - e.g. content
    - But then we would have duplicate
      - section[up-main=zone]?
Maybe all guardEvents should have a loadPage() method
- So it's more discoverable then event.loadPage()
Consider publishing { dataMap, placeholderMap, previewMap } as @experimental
- Check if we have tests here
- Check whether a single { map } option (or an object target) would be superior
  - up.render({ target: { '.foo': { data: { key: 123 }, placeholder: 'spinner' }, '.bar': {} }, url: '/path' })
  - up.render({ target: { '.foo, .bar' }, dataMap: { '.foo'. { key: 123 } }, placeholderMap: { '.foo': 'spinner' }, url: '/path' })
  - up.render({ target: { '.foo, .bar' }, map: { '.foo'. { data: { key: 123 }, placeholder: '.spinner' } }, url: '/path' }) => Doing something to the primary is a very common use case and great now
Consider publishing up.script.clean()
- Would we need a fallback for { layer }?
- Supporting the use case "recompile later" is hard because then we would need to update the idempotent-compiler-fn-tracking
Consider removing { content } option of createFromSelector(), affix(), etc. in favor of a third argument for constructing nested things
- When we make this change we should also fix the inconsistency that a string arg is considered HTML, but Array is considered text (and will be escaped)
Allow to set custom close animation from link
- Also support (or document?) up.layer.open({ closeAnimation })
Consider contracting more attributes into shorthand values
- E.g. [up-emit] and [up-emit-props] should be just one thing
- E.g. [up-scroll] and [up-scroll-behavior] should just be one thing (but what about all the reveal attributes? reveal-snap/top/pading/max)
- E.g. [up-transition] and [up-easing] and [up-duration] should just be one thing
Evtl. sollte [up-back] den letzten History-Eintrag im Root (?)-Layer nehmen?
- Back vs. Modals allgemein betrachten
In the layer config, openAnimation and closeAnimation is a function, but it receives no useful args
- Give it { layer, value }
- Document it
Consider up.RenderResult#primary or up.RenderResult#fallback
- Updating ":main" via { fallback: true } must yield #primary === true
- So maybe #primary, #expected, #intended or similiar is a better name than #fallback
Rename "loading partial" to "filling partial" or similiar
- up:partial:fill
- up.partial.fill()
- So "load" remains the term for sending a request
- So we can offer [up-on-fill]
Consider X-Up-Redirect so we can get rid of param-transporting in unpoly-rails
- Unpoly would track all X-Up params of request and response

Next release

@stable

Previews

Do we need to publish parseNodesFromHTML() so people can build their own template handler?
- Yes, we mention in the docs
- Should probably be createNodesFromHTML()
Set layer.current to the base layer when applying and reverting previews

Demo

The demo is broken
Make sure form group validation still works after Bootstrap 5 Upgrade
Set tour bubbles for the new functionality

Cards

Make a skeleton for cards

Guide

Skeleton for menu
Skeleton for main area

Docs & CHANGELOG

CHANGELOG
- up.Request#ended
- Native :has() is required and the app will not boot without
- Explain that the demo shows new optimistic rendering, check "Extra latency"
- badResponseTime => lateDelay
  - config.lateDelay
  - { lateDelay }
  - [up-late-time]
- Go through entire Git log
- Explain that we are now smarter at splitting complex selectors at
- Explain that tokens now default to comma-separation
  - Comma is canonical
  - Space-separation still possible in most cases
  - or-separation is deprecated
  - Also make sure to update doc pages!
  - This affects
    - [docs updated] [up-show-for]
    - [docs updated] [up-hide-for]
    - [docs updated] [up-scroll]
    - [docs updated] [up-focus]
    - [docs updated] [up-layer] or { layer }
    - [docs updated] up.on()
    - [docs updated] URLPatterns
      - [up-alias]
      - [up-dismissable], { dismissable }
      - [up-accept-location]
      - [up-dismiss-location]
      - up.cache.expire()
      - X-Up-Expire-Cache
      - [up-expire-cache] { expireCache }
      - up.cache.evict()
      - X-Up-Evict-Cache
      - [up-evict-cache] { evictCache }
X-Up-Target should mention (in the first paragraph) that it is both request and response header
Document [up-placeholder] and [up-preview] in up.status (main), up-follow and up.render()
Docs for up.Preview class and its methods
- up.Preview#insert (and up.fragment.insertTemp()) must mention that:
  - The element is compiled and destroyed
  - An attached element is moved back to its original position (and not compiled or destroyed)
  - You can refer to a template
"Network issues" should talk about previews and placeholders under "Slow server responses"
- Right now they only talk about feedback classes
Change with disabling
- We now support { disable: Element }
- We now support { disable: Array<Element|string> }
- Disabling forms from links
  - Document that [up-disable] is now also available for [up-follow]
  - Document that options.disable is now supported for up.follow()
  - Add a section to /disabling-forms
Update render lifecycle
- Callback table
Doc page for
- Compile with data
- Inline data
- Manipulate in onRendered
- Templating engine
Doc page /loading-state "Showing loading state"
- Show how the preview can manipulate the DOM
  - Prefer to be additive
- Show how the preview can inspect the context
- Examples
  - Example: Placeholder
  - Example: Add a TODO
- Previews are not applied when we have cached content to render
  - Also not shown when cache-then-revalidate
- Multiple preview effects
  - Space-separated
  - Array
- Reverting effects
  - undo()
  - returning destructor
  - Important: don't revert effects that you didn't cause
    - Check if you need to do something
    - All up.Preview methods do this
- Placeholders
  - As embedded HTML
  - As template cloning
  - As function call in a preview
  - Placeholder for OpenLayer change will open a new temporary layer
    - This will be reverted in case the server renders unexpected content
  - Dynamic placeholders with embedded data object
- Dynamic previews/placeholders
  - Placeholders
    - #template as .modifier syntax
    - Explain that you can compile template clones
    - Explain that you can always use [up-preview] or [up-preview-fn].
  - Previews can take arguments
  - In JavaScript you can use { preview: Function } or { placeholder: Function }
- Built-in previews
  - Just a short list with links to existing docs
    - Disabling forms while working
      - Link to disabling
    - Marking active elements with classes
      - Link to .up-active
      - Link to .up-loading
    - Placeholders
    - Progress bar for late responses
      - Link to progress bar
- While watching
  - [up-watch-disable]
  - [up-watch-preview]
- Delaying previews
```
up.preview('foo', (preview) => {
  up.util.timer(1000, function() {
    if (!preview.ended) {
      preview.run('other')      
    }
  })
}) 
```
- Optimistic rendering
  - Point to demo example & code
  - Signaling severe network problems (up:fragment:offline)
- Showing loading state
Rename /loading-indicators to /progress-bar ?
- Extract anything that is not about the progress bar
Rework the section "Styling active elements" in /up-active.
- It should link to the new status guides
Rename up.feedback to up.status
- Title "Status effects"
- Package intro should summarize our fancy new doc pages
Doc page /navigation-bars
- Redirect /nav-bars /nav-bar /navbars /navbar /nav
Document new render options
- Do this after we have the new doc pages
- up.render()
  - Document { preview: string|Function|Array<string|Function> }
  - Document { revalidatePreview }
  - Document { placeholder: string|Function|Element }
    - It also opens a new layer
- [up-follow]
  - Document [up-preview]
  - Document [up-revalidate-preview]
  - Document [up-preview-fn]
  - Document [up-placeholder]
    - It also opens a new layer
- HTML options ({ content, fragment, placeholder })
  - also allow a template
  - Also accept a function (is this tested?)
  - Accept a List
New watch/validate options
- Document [up-watch-preview] and [up-watch-placeholder] wherever we also document [up-watch-disable] or [up-watch-feedback]
  - [up-watch]
  - up.watch()
  - [up-validate]
  - up.validate()
  - [up-autosubmit]
  - up.autosubmit()
- Extend /watch-options with [up-watch-preview] and [up-watch-placeholder]
- Watcher callbacks get { disable, preview, feedback, placeholder } options to pass on to rendering
  - With up.watch()
  - With [up-watch]
/opening-overlays and [up-layer=new] should say how to open an overlay from local content
- String
- Extract segments from /providing-html
- [up-defer] supports [up-preview], [up-placeholder]
  - The docs already talk about fallback state. We could destinguish "while it's loading".
- [up-poll] supports [up-preview], [up-placeholder]
- Consider an authentication modal in https://unpoly.com/up:fragment:loaded#changing-render-options
- Check if the unpoly.com homepage needs to mention status effects and optimistic rendering
  - Instantly respond with loading state, render optimistically, handle offline
- Checken dass @see auf den Module-Pages die wichtigsten Sachen enthält
- up:request:loaded should say it's low level and consider up:fragment:loaded instead

Name		Name	Last commit message	Last commit date
Latest commit History 67 Commits
.github		.github
bin		bin
manual_tests		manual_tests
.gitignore		.gitignore
todo.md		todo.md
v4.md		v4.md
view-transitions.md		view-transitions.md

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Repository files navigation

Priority

Perspective

Next release

Previews

Demo

Cards

Guide

Docs & CHANGELOG

Release

Backlog

Documentation

Icebox / Tar pits

About

Releases

Packages

Languages

unpoly/unpoly-backlog

Folders and files

Latest commit

History

Repository files navigation

Priority

Perspective

Next release

Previews

Demo

Cards

Guide

Docs & CHANGELOG

Release

Backlog

Documentation

Icebox / Tar pits

About

Resources

Stars

Watchers

Forks

Releases

Packages 0

Languages

Packages