Oliver Kopp

This somehow refs https://github.com/koppor/jabref/issues/85, where I described a way to avoid crossref (which is contradicting the proposal here)

> I think what you implemented was already possible before by unchecking "Entry table > Fit table horizontally on screen" in the preferences (except if I misunderstood what you were...

Windows Explorer:   Double click should set the optimum width: 

DevCall decision: Merge and work on column resizing afterwards. Probably with the magic button as in Windows Explorer.

Is this really the first time, I want to delete code and @tobiasdiez wants to keep it? 😇 @DominikVoigt and I worked hard to keep the smart resize. Here it...

We had some WTF moments with minwidth 10, 29. We tried with 80: 

We hit https://stackoverflow.com/a/47860355/873282. @koppor @DominikVoigt : Look at #7209. Should be easy Expected behavior: double click: "optimal" column width. Iterate on content an choose the maximum content length as prefWidth.

We proceed as follows: 1. @calixtus resolves merge conflicts 2. Manual test of new system 3. Merge 4. Tests will come as follow up (otherwise, this won't happen until August...

> After a little bit testing, I made those observations: > > * Minimal column width is too large: my year column is three times to big at minimum size....

I think, this issue should be handled differently: - If a selection of JabRef leads to the fact that the entry of the entry editor is not in the table...