Timeline for New Feature: Table Support
Current License: CC BY-SA 4.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 30, 2020 at 15:16 | comment | added | VLAZ | @TylerH hence my wish for some convenience tool that helps. When adding code in an answer, we can use a stack snippet. It's a bit of a hack if the code is not actually meant to be runnable but it does allow you to more easily edit it if it's too wide, since you can scroll left/right in the editor window. Then you can delete the starting snippet tag and you're left with just a code block. A more complex table like here becomes very hard to edit. 3-column view | view with your CSS | |
| Nov 30, 2020 at 15:01 | comment | added | TylerH | @VLAZ Well trying to scroll an input box wider than your monitor only makes as much sense as wanting to view a box wider than your monitor, so that doesn't seem like much of a concern :-P | |
| Nov 30, 2020 at 14:49 | comment | added | VLAZ | @TylerH not sure it's a great solution, either. When I use a vertical monitor, I don't have much extra space to the side. When I use a horizontal monitor, I use the three columns editor userscript which splits the page in three and shows the question (left panel), the answer box (middle panel), and answer preview (right box). Looks like this. So, I'm not sure it's a great idea to make the box wider. I already use a text editor if the content is wider. | |
| Nov 30, 2020 at 14:45 | comment | added | TylerH |
@VLAZ Ah, bummer. While SO should fix that, it can be user-fixed w/ a user style with the following CSS selector/properties: textarea { resize: revert !important; position: relative; z-index: 1; }
|
|
| Nov 30, 2020 at 14:41 | comment | added | VLAZ | @TylerH resizable up/down but not left/right. Screenshot. | |
| Nov 30, 2020 at 14:31 | comment | added | TylerH | @VLAZ isn't the editor window resizeable? | |
| Nov 24, 2020 at 7:36 | comment | added | VLAZ | Honestly, my biggest fear about this. I like using tables when it makes sense and I just generate them. Saves me a lot of hassle. Making sure to manually format the table correctly sounds like a slow torture when the editor screen is slightly too small to fit the whole thing and you're trying to add one more column. I do hope some sort of convenience tool emerges. | |
| Nov 23, 2020 at 20:41 | comment | added | ben is uǝq backwards | Editing badly formatted tables is already one of the more tedious tasks (that and disentangleing error stacks that got munged when someone used quotes instead of code to highlight them). At least now the tables will look pretty afterwards. | |
| Nov 23, 2020 at 18:45 | comment | added | Cave Johnson | yea and it will probably be worse if they include a button to generate the table code, which I think is in the new editor which is going to be rolled out. | |
| Nov 23, 2020 at 18:29 | comment | added | bad_coder |
@KodosJohnson posters experienced with Markdown derivatives aren't the ones I'm worried about. It's the inexperienced members who will likely post broken tables (that will be left for others to fix.) I like the idea, it's a game changer.
|
|
| Nov 23, 2020 at 18:21 | comment | added | Cave Johnson | IMO the sort of people who go through the hassle of formatting with tables will probably double check that it is formatted correctly. | |
| Nov 23, 2020 at 18:15 | history | answered | bad_coder | CC BY-SA 4.0 |
