Table column headers are not visible in downloaded SVG

GoJS
1

The column headers are not visible in downloaded SVG, please check the below attached details.

Code used to generate column headers:

$(go.Panel, “Table”,
{
stretch: go.GraphObject.Fill, //height:25,
alignment: go.Spot.Left,
margin: new go.Margin(0.5, 0, 0, 0),
},
new go.Binding(“background”, “isSelected”,
(sel, shp) => shp.part.data?.nodedetails?.tablebackgroundcolor || “white”).ofObject(),
$(go.RowColumnDefinition,
{
row: 1,
},
new go.Binding(“background”, “isSelected”,
(sel, shp) => shp.part?.data?.nodedetails?.color || “white”).ofObject(),
),
$(go.TextBlock,“”,   {     row:1,     width:49,     height: 18,     name: “IndexHeader”,     text: “Sr.No.”,     column: 0,     font: “bold 11pt sans-serif”,     alignment: go.Spot.Left,     textAlign: “left”,     wrap: go.Wrap.None,     margin: new go.Margin(2, 0, 1, 0)   },   new go.Binding(“background”, “isSelected”,     (sel, shp) =>  shp.part?.data?.nodedetails?.color || “white”).ofObject(), ), $(go.TextBlock,“”,   {   row:1,   height: 18,   name:“BLHeader”,   text:“Business Logic List”,   column: 1,   alignment: go.Spot.Left,   textAlign: “left”,   font: “bold 11pt sans-serif”,   wrap: go.Wrap.None,   margin: new go.Margin(2, 0, 1, 0) },   new go.Binding(“width”, “”, setBlColumnAndScrollingTableWidth).ofObject(),   new go.Binding(“background”, “isSelected”,     (sel, shp) =>  shp.part?.data?.nodedetails?.color || “white”).ofObject(),   ), $(go.TextBlock,“”,   {   row:1,   width:69,   height: 18,   name:“ModifiedHeader”,   text:“Modified”,   column: 3,   alignment: go.Spot.Left,   textAlign: “left”,   font: “bold 11pt sans-serif”,   wrap: go.Wrap.None,   margin: new go.Margin(2, 0, 1, 0)   },   new go.Binding(“background”, “isSelected”,     (sel, shp) => shp.part?.data?.nodedetails?.color || “white”).ofObject(), ), $(go.TextBlock,“”,   {   row:1,   height: 18,   name:“RuleTypeHeader”,   text:“RuleType”,   visible:true,   column: 2,   alignment: go.Spot.Left,   textAlign: “left”,   font: “bold 11pt sans-serif”,   wrap: go.Wrap.None,   margin: new go.Margin(2, 0, 1, 0) },   new go.Binding(“width”, “”, setRuleTypeHeaderWidth).ofObject(),   new go.Binding(“background”, “isSelected”,     (sel, shp) => shp.part?.data?.nodedetails?.color || “white”).ofObject(),   ),)

Original diagram view:

image
image1125×421 28 KB

Diagram view after download SVG:

image
image875×372 7.84 KB

2

Thank you for the detail. We’ll investigate this and get back to you.

3

We have fixed the issue here but we need to look into a related SVG issue before we make the next release. I expect we’ll have a release by Monday.

4

We’ve just released 3.1.2, it should fix this issue. Thank you again for reporting.

5

Hi Simon,
The release version is working for me.
I have one more question regarding the scroll bar, search box of a scrolling table in SVG and license key.

 1. After upgrading the GoJS version from **3.0.11** to **3.1.2**, the previously implemented license key no longer works, and a watermark is now visible. Do I need to renew my license?

image
image495×210 11 KB

  1. Is it possible to make the scroll bar functional and use the search box to filter data inside the table in the downloaded SVG?
    If scrolling is not possible, then please provide options to automatically stretch the table to fit all the data.
6
  1. Whenever upgrading a major version (i.e. 2 to 3) or a minor version (i.e. 3.0 to 3.1), you’ll need to get a new license key, at: Product Activation
  2. The SVG produced by Diagram.makeSvg is meant to be a static image. A viewer of SVG cannot interact with it, for example to scroll or zoom or show context menus or copy or delete nodes or draw new links.
    However, I cannot say that it would be impossible for you to implement such behavior, but please realize that for security reasons such scripting behavior is usually restricted by various SVG renderers. I don’t know what the current state is for scripting behavior within SVG – it’s been over 20 years since I’ve implemented such behavior successfully.
7

Ok got it.
Were there any performance-related improvements when using Avoids Nodes in the new version?

8

Since 3.0.11? I don’t know – it’s possible but not obvious in reviewing the changes since then.