Bauke Scholtz

Re-reading the *"would have been removed"*, are you saying that it's totally fine to remove these without deprecation?

Let's move to 5.0 for now. We can then take the opportunity to reconsider the f:metadata. Also related: https://github.com/jakartaee/faces/issues/1849

### History Initially, ui:repeat had only `offset`/`size`/`step` attributes. However, this didn't allow to iterate a predefined amount of times. I.e. the following attempt to render 10 divs didn't work because...

@arjantijms @tandraschko @volosied +1 or -1 for [**4.1 spec update proposal**](https://github.com/jakartaee/faces/issues/1713#issuecomment-1336163691)? And the support for a negative step?

Ok sure.

How about the support for a negative step? > Optional: support a negative step. I.e. step="-1" will iterate backwards. This will be a new feature. This can be very useful...

I think this is great if it also allows external URLs. Old ``` public void action() throws IOException { // ... FacesContext.getCurrentInstance().getExternalContext().redirect("https://google.com"); } ``` New (just match `^https?://`) ``` @Redirect("https://google.com")...

I'd rather not implement/advocate a "forward" for now. It only encourages poor practices.

Hmm, it makes indeed sense to let h:html extend from f:view/UIViewRoot. But this will be a breaking change. Wondering why this was not done from the beginning on.

Oh cool. Let's do it for 5.0. I like you took the opportunity to finally turn the PhaseId into an enum.