https://bugs.documentfoundation.org/show_bug.cgi?id=173335
--- Comment #7 from Eyal Rozenberg <[email protected]> --- (In reply to Heiko Tietze from comment #3) > for just one use case. Is it, though? I will posit the following: In the _default_ use case, or the most common use cases, having AutoFilter enabled is a positive thing. It does not prevent me from editing the CSV, and it facilitates examining/exploring it. And the AutoFilter is not invasive unless you intentionally do something with it. Can you present a use case in which AF is disruptive/detrimental? (I will grant you that without a line of column headers, I find it less useful; and we don't currently have any detection heuristic for that IIANM.) > It bloats the import dialog 1. I believe there is currently room in the dialog for it: The "Other Options" has 4 options out of 6 which fit the dialog width. 2. I might consider just enabling this by default even without the explicit option in the dialog (with an option in Tools > Options instead). But - only when we decide there's a header row. > -1 since AF is just one out of many functions that users can ask for. What other function do you believe it is likely for a user to want to apply immediately? > And AF'ing a table is just one click or shortcut (ctrl+shift+L). Well, that argument works both ways, removing the AF is just one click or shortcut away... (In reply to Peter from comment #2) > Maybe one more thing. If I have a CSV file open, and hit File->Reload, It > would be great if it would preserve the current filters. I believe that should be a separate bug. -- You are receiving this mail because: You are the assignee for the bug.
