The Starboard Oak trim on the centreboard case broke away at Cobnor, long story. When I chiselled the remains of it off I discovered the case plywood (9mm) was slightly damp. I scraped out as much as possible (maybe 20mm deep), dried it with a heat gun, treated it with Ronseal Wet Rot Restorer, sanded it, primed with thin epoxy then filled with thickened epoxy.
Sealing the ply is mission critical, because rebuilding the case would be a mountain of work. Then I'll look at gluing a new keel and screwing it into the strong hog with stainless screws.
I have a selection of wood: many Oak kitchen door frames, strips of Oak, ten Teak blocks that I rescued from the neighbours wood stove pile (the blocks are a school window frame chopped up!),
four Teak lengths that I bought from Robbins at Beale for £15 each, plenty of what Richard called Red Mahogany.
I would appreciate advice on the best wood to use for the keel, how to fix it and how to seal it.
Teak seems logical, I have enough to replace the Oak trim on the skeg and make the entire keel from Teak. But I have no experience of using Teak.
Paul Fisher's plans included Iroko runners which I never fitted. But long hardwood runners would strengthen the 6mm ply hull which over the years has twice splintered internally. Perhaps Red Mahogany would be ok for runners?
Cheers
Paul
- Safari Chrome Compatibility Nabble Forums And More Accurate
- Safari Chrome Compatibility Nabble Forums And More Beautiful
-->APPLIES TO: SQL Server 2016 Reporting Services and later Power BI Report Server
- Today’s web landscape heavily favors browsers based on Chromium, which of course includes Google Chrome, but also the new Microsoft Edge, as well as Opera, Vivaldi, Brave, and quite a few more.
- Firefox and Chrome are two market leaders among browsers, but which is the better fit for you? In this Firefox vs Chrome battle we try and answer this question through gladiatorial combat, so join.
Keep in mind that, though Safari will appear to be another browser, it won't actually be that browser. Any web app or site that requires, say, Chrome's Blink rendering engine (which Safari doesn't have) won't work properly, even if Safari's user agent is changed to Google Chrome. Here's how you go about changing the user agent in Safari. I can't reproduce this problem, so it is difficult to understand what is going on. Based on the information you posted, I see that the nabble URL has been truncated. It should end with '.n2.nabble.com', but it ends with '.n2.na'. Maybe you could change the name of the forum to make the URL shorter and see if it works.
Learn about what browser versions are supported for managing and viewing SQL Server Reporting Services, the ReportViewer Controls and Power View.
Note
Reporting Services integration with SharePoint is no longer available after SQL Server 2016.
Browser requirements for the web portal
The following is the current list of browsers supported for the web portal.
Microsoft Windows
Windows 7, 8.1, 10; Windows Server 2008 R2, 2012, 2012 R2
- Microsoft Edge (+)
- Microsoft Internet Explorer 10 or 11
- Google Chrome (+)
- Mozilla Firefox (+)
Apple OS X
OS X 10.9-10.11
- Apple Safari (+)
- Google Chrome (+)
- Mozilla Firefox (+)
Apple iOS
iPhone and iPad with iOS 9
- Apple Safari (+)
Google Android
Phones and tablets with Android 4.4 (KitKat) or later
- Google Chrome (+)
(+) Latest publicly released version
Browser requirements for the ReportViewer web control (2015)
The following is the current list of browsers supported with the ReportViewer web control (2015). The report viewer supports viewing reports from Reporting Services web portal and SharePoint libraries.
Microsoft Windows
Windows 7, 8.1, 10; Windows Server 2008 R2, 2012, 2012 R2
- Microsoft Edge (+)
- Microsoft Internet Explorer 10 or 11
- Google Chrome (+)
- Mozilla Firefox (+)
Apple OS X
OS X 10.9-10.11
- Apple Safari (+)
(+) Latest publicly released version
If you are using a SharePoint product that is integrated with Reporting Services, see Plan browser support in SharePoint 2016.
Authentication requirements
Browsers support specific authentication schemes that must be handled by the report server in order for the client request to succeed. The following table identifies the default authentication types supported by each browser running on a Windows operating system.
| Browser type | Supports | Browser default | Server default |
|---|---|---|---|
| Microsoft Edge (+) | Negotiate, Kerberos, NTLM, Basic | Negotiate | Yes. The default authentication settings work with Edge. |
| Microsoft Internet Explorer | Negotiate, Kerberos, NTLM, Basic | Negotiate | Yes. The default authentication settings work with Internet Explorer. |
| Google Chrome(+) | Negotiate, NTLM, Basic | Negotiate | Yes. The default authentication settings work with Chrome. |
| Mozilla Firefox(+) | NTLM, Basic | NTLM | Yes. The default authentication settings work with Firefox. |
| Apple Safari(+) | NTLM, Basic | Basic | Yes. The default authentication settings work with Safari. |
(+) Latest publicly released version
Script requirements for viewing reports
To use the report viewer, configure your browser to run scripts.
If scripting is not enabled, you will see an error message similar to the following when you open a report:
- Your browser does not support scripts or has been configured to not allow scripts to run. Click here to view this report without scripts.
If you choose to view the report without script support, the report is rendered in HTML without report viewer capabilities such as the report toolbar and the document map.
Note
The report toolbar is part of the HTML Viewer component. By default the toolbar appears at the top of every report that is rendered in a browser window. The report viewer provides features include the ability to search the report for information, scroll to a specific page, and adjust the page size for viewing purposes. For more information about the report toolbar or HTML Viewer, see HTML Viewer and the Report Toolbar.
Browser support for ReportViewer web server controls in Visual Studio
The ReportViewer Web server control is used to embed report functionality in an ASP.NET web application. The controls are included with Visual Studio and support different browsers and browser versions than the other components described in this topic. The type of browser used to view the application determines the kind of ReportViewer functionality that you can provide in your application. Use the table provided in this topic to determine which of the supported browsers are subject to report functionality restrictions and the supported platforms.
Use a browser that has script support enabled. If the browser cannot run scripts, you cannot view the report.
Microsoft Windows
Windows 7, 8.1, 10; Windows Server 2008 R2, 2012, 2012 R2
- Microsoft Edge (+)
- Microsoft Internet Explorer 10 or 11
- Google Chrome (+)
- Mozilla Firefox (+)
(+) Latest publicly released version
Power View browser support
Microsoft Windows
Windows 7, 8.1, 10; Windows Server 2008 R2, 2012, 2012 R2
- Microsoft Internet Explorer 10 or 11
- Mozilla Firefox (+)
Apple OS X
OS X 10.9-10.11
- Apple Safari (+)
(+) Latest publicly released version
Safari Chrome Compatibility Nabble Forums And More Accurate
For more information on the SharePoint 2016 browser support, see Plan browser support in SharePoint 2013.
Next steps
Finding and Viewing Reports in the web portal
Reporting Services Tools
Web portal (SSRS Native Mode)
HTML Viewer and the Report Toolbar
URL Access Parameter Reference
Safari Chrome Compatibility Nabble Forums And More Beautiful
More questions? Try asking the Reporting Services forum