Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 0.9.4

Bug #12053 With SetVersion(8) setting bottom border color to 0 gives cross borders (!)
Submitted: 2007-09-14 12:49 UTC
From: gwinkless Assigned: cschmitz
Status: Closed Package: Spreadsheet_Excel_Writer (version 0.9.1)
PHP Version: 4.3.2 OS: Linux Redhat 9 (Shrike)
Roadmaps: (Not assigned)    

 [2007-09-14 12:49 UTC] gwinkless (Geoff Winkless)
Description: ------------ Using SetVersion(8) and then setting the bottom border with a numerical 0 sets the cross borders (not sure what they're called) so the cells appear to have X's over them. Using "black" or "0" (in quotes) solves this problem, but that's not really ideal. Note that using "null" produces the same result, which might suggest some test for === rather than == might be useful? Test script: --------------- <?php require_once ("Spreadsheet/Excel/Writer.php"); $WB =& new Spreadsheet_Excel_Writer(); $WB->setVersion(8); $sheet =& $WB->addWorksheet(); $sheet->write(0, 0, "0", $WB->addFormat(array("bordercolor"=>0, "border"=>1))); $sheet->write(0, 1, "\"0\"", $WB->addFormat(array("bordercolor"=>"0", "border"=>1))); $sheet->write(0, 2, "black", $WB->addFormat(array("bordercolor"=>"black", "border"=>1))); $sheet->write(0, 3, "null", $WB->addFormat(array("bordercolor"=>"null", "border"=>1))); $WB->send("test.xls"); $WB->Close(); ?> Expected result: ---------------- Spreadsheet "test.xls" sent to browser, containing four cells, (0, "0", black, null), three with black borders and the fourth perhaps undefined (setting a border with no color might reasonably produce undefined results). Actual result: -------------- Spreadsheet "test.xls" sent to browser, containing four cells, (0, "0", black, null), all with black borders but with the 0 and null cells crossed out.


 [2009-11-29 08:32 UTC] cschmitz (Carsten Schmitz)
-Status: Open +Status: Closed -Assigned To: +Assigned To: cschmitz
This bug has been fixed in SVN. If this was a documentation problem, the fix will appear on by the end of next Sunday (CET). If this was a problem with the website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better.