Ricardo M.
Ricardo M.
Pending to check what would be the difference between: 1. no errorHandler defined 2. default errorHandler 3. noErrorHandler
unfortunately, it won't, the e2e tests run with Chrome by default :cry:, in any case, I think the most relevant part here would be to be able to take screenshots...
Technically it's a collapsed container :grimacing: , we could probably extend the check to evaluate whether the container has children or not
``` types: out: mediaType: application/json ```
Seems to be working now with the new Form 
Closing it as already implemented as part of the new form library. 
Finally, we got our priorities right :smile: :heart_hands: :rocket: Upvoting for this feature +1000
@icidasset, that could be a good idea; the downside, perhaps, could be how to wire different components together. For instance, connecting the "maximize button" with the "window component". Or maybe...
Ah, right, I forgot about the events. I guess that would be enough to let's say, clicking on the maximize button will increase the `` element to fill the available...
This seems to be working now 