roost | Proof of Concept for Eventsourced backend | Networking library

To prevent things from being bumped down you will need to pull the dropdown playlist out of the document flow, with position:absolute

You could use position: relative instead of absolute on the .collapsibleWrapper element. Reposition as necessary

The code would be more manageable using stylesheet. as shown.

To move the "Zelda Playlist" right below the button, all you need is a wrapper that encapsulates the button and the playlist.

After that, migrate the positioning css from the button to the wrapper (position of any element is block by default, which means if the button is above the playlist within the wrapper, the button and playlist is vertically-aligned by default).

Set to right:5% instead of left: 95%, this allows the wrapper items to align right by default.

Set the button to float right and margin-left:100% to ensure that it's on the right side.

Set collapse div to 100% to ensure that the whole collapsed div is not shrunk

You will need to turn these strings into vectors, and pad them to equal length. I'll show you an example with just partial_x_train_actors_array:

Html is all to do with structure from what i learned. Maybe try spacing out your html to make it easier to read (trust me it will save time in the long run, when looking for small mistakes) Try using some sort of a text editor to get the idea of clean html into your head always helps. Also not too sure why you have a footer tag embedded, the tag is usually used for copyright stuffs etc. If your looking to decrease the size of the text just use css. Rule of thumb css appearance html structure.

Just put an id on what text you want to make smaller and change the font size in your css later. Saves you using the unnecessary footer tag

assuming that your input is (with lines)

The way you build test is very particular. This is not a Spatial object, which makes it particular to use...
The way you use combn is not correct. It can not use a list of objects like this. The documentation says:

?combn
x vector source for combinations, or integer n for x <- seq_len(n).

So you should use it as is. The example and data you give is not easy to be used as is. I had to modify differents things. Next time, you should provide a simple example that corresponds to your data problem. Refer to: How to make a great R reproducible example?
As far as I can understand from what your looking at, I propose you a possible way. But you need to learn what is the organization of SpatialPolygons objects in R to make your script cleaner.

So here, I use combn in a usable way. I retrieve all polygons intersections in a list as you did. When the intersection is not NULL, I also retrieve it as a Polygons object to be able to gather all Polygons as a SpatialPolygons: