You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Create a new file and insert some value to Sheet1, set autofilter to header row
(ex. f.AutoFilter("Sheet1", "A1", "E1", "") ) then save the file.
Open file, choose Sort A to Z (or Z to A) on the filter and the excel window will freeze, can't do anything.
(but if choose some text filter first then sort won't cause this problem)
Output of go version:
go version go1.13.5 windows/amd64
Excelize version or commit ID:
excelize v2.2.0
Environment details (OS, Microsoft Excel™ version, physical, etc.):
Happened on both Excel 2007 and 2013 (don't know if other version would happen too)
The text was updated successfully, but these errors were encountered:
Hi, thanks for the nice work,
but there is a problem after upgraded to the master branch, don’t known if related.
I have a web app that let user download excel, and the autofilter works fine at the first download, then it will get Removed Feature: Named range from /xl/workbook.xml part (Workbook) error for every downloaded excel, after recover it, the problem of the issue happened again, any thought?
edit:
Solved it, have to delete default Sheet1 first then set autofilter.
Jerome1337
pushed a commit
to Jerome1337/excelize
that referenced
this issue
Jun 16, 2020
Description
AutoFilter will freeze the excel window.
Steps to reproduce the issue:
Create a new file and insert some value to Sheet1, set autofilter to header row
(ex.
f.AutoFilter("Sheet1", "A1", "E1", "")
) then save the file.Open file, choose
Sort A to Z
(or Z to A) on the filter and the excel window will freeze, can't do anything.(but if choose some text filter first then sort won't cause this problem)
Output of
go version
:Excelize version or commit ID:
Environment details (OS, Microsoft Excel™ version, physical, etc.):
Happened on both Excel 2007 and 2013 (don't know if other version would happen too)
The text was updated successfully, but these errors were encountered: