Skip to content

Commit b3b93e1

Browse files
TiLiedTiLied
committed
Updated Microsoft.CodeAnalysis.CSharp to 4.8.0
Updated generated csharp and xml docs.
1 parent 2576a20 commit b3b93e1

File tree

7,363 files changed

+86806
-62
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

7,363 files changed

+86806
-62
lines changed

‎CSharpToJavaScript/APIs/JS/Generated/JS.generated.cs‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
//22.10.2023 19:25:19
1+
//02.12.2023 13:14:55
22
using static CSharpToJavaScript.APIs.JS.GlobalObject;
33
using CSharpToJavaScript.Utils;
44
using System.Collections.Generic;

‎CSharpToJavaScript/CSTOJS.cs‎

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -473,7 +473,6 @@ private void Generate(SyntaxTree? tree, Assembly assembly, List<MetadataReferenc
473473
.AddReferences(references.ToArray())
474474
.AddSyntaxTrees(trueST);
475475

476-
477476
_Walker = new(this, compilation.GetSemanticModel(trueST));
478477

479478
_Walker.JSSB.Append(Options.AddSBInFront);

‎CSharpToJavaScript/CSharpToJavaScript.csproj‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@
2020
</PropertyGroup>
2121

2222
<ItemGroup>
23-
<PackageReference Include="Microsoft.CodeAnalysis.CSharp" Version="4.7.0" />
23+
<PackageReference Include="Microsoft.CodeAnalysis.CSharp" Version="4.8.0" />
2424
</ItemGroup>
2525

2626
<ItemGroup>

‎CSharpToJavaScript/Utils/Docs/.generated.xml‎

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,10 @@
11
<docs>
2-
<XSLTProcessorGenerating_HTML>
2+
<XSLTTransforming_XML_with_XSLTThe_Netscape_XSLT_XPath_ReferenceAxesSelf>
33
<summary>
4-
One common application of XSLT in the browser is transforming XML into HTML on the client. This example will transform the input document (example2.xml), which contains information about an article, into an HTML document.
4+
The self axis indicates the context node itself. It can be abbreviated as a single period (<c>.</c>).
55
</summary>
66
<remarks>
7-
<para>The <c>&amp;lt;body&amp;gt;</c> element of the article now contains HTML elements (a <c>&amp;lt;b&amp;gt;</c> and <c>&amp;lt;u&amp;gt;</c> tag). The XML document contains both HTML elements and XML elements, but only one namespace is needed, namely for the XML elements. Since there is no HTML namespace, and using the XHTML namespace would force the XSL to create an XML document that would not behave like an HTML document, the <c>xsl:output</c> in the XSL Stylesheet will make sure the resulting document will be handled as HTML. For the XML elements, our own namespace is needed, <c>http://devedge.netscape.com/2002/de</c>, and it is given the prefix myNS <c>(xmlns:myNS=&amp;quot;http://devedge.netscape.com/2002/de&amp;quot;)</c>.</para>
8-
<para><seealso href="https://developer.mozilla.org/en-US/docs/Web/API/XSLTProcessor/Generating_HTML"> <em>See also on MDN</em> </seealso></para>
7+
<para><seealso href="https://developer.mozilla.org/en-US/docs/Web/XSLT/Transforming_XML_with_XSLT/The_Netscape_XSLT_XPath_Reference/Axes/self"> <em>See also on MDN</em> </seealso></para>
98
</remarks>
10-
</XSLTProcessorGenerating_HTML>
9+
</XSLTTransforming_XML_with_XSLTThe_Netscape_XSLT_XPath_ReferenceAxesSelf>
1110
</docs>

‎CSharpToJavaScript/Utils/Docs/Accessibility/Accessibility.generated.xml‎

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
<docs>
2+
<Accessibility>
3+
<summary>
4+
For many people, technology makes things easier. For people with disabilities, technology makes things possible. Accessibility means developing content to be as accessible as possible, no matter an individual&amp;apos;s physical and cognitive abilities and how they access the web.
5+
</summary>
6+
<remarks>
7+
<para>&amp;quot;<strong>The Web is fundamentally designed to work for all people</strong>, whatever their hardware, software, language, location, or ability. When the Web meets this goal, it is accessible to people with a diverse range of hearing, movement, sight, and cognitive ability.&amp;quot; (<see href="https://www.w3.org/standards/webdesign/accessibility">W3C - Accessibility</see>)</para>
8+
<para>-<see href="https://www.w3.org/WAI/about/groups/waiig/">WAI Interest Group</see><br/>-<see href="https://developer.mozilla.org/en-US/docs/Web/Guide">Developer guides</see><br/></para>
9+
<para><seealso href="https://developer.mozilla.org/en-US/docs/Web/Accessibility"> <em>See also on MDN</em> </seealso></para>
10+
</remarks>
11+
</Accessibility>
12+
</docs>

‎CSharpToJavaScript/Utils/Docs/AccessibilityArchitecture/AccessibilityArchitecture.generated.xml‎

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
<docs>
2+
<AccessibilityArchitecture>
3+
<summary>
4+
Mozilla exposes a document containment hierarchy with text and embedded objects. Sometimes the embedded object is really just another text container with more embedded objects.
5+
</summary>
6+
<remarks>
7+
<para>However in accessibility hierarchies such as ATK and IAccessible2, text is not exposed in leaf nodes as it is in a W3C DOM. The text is actually exposed via a special text interface in the parent of the text nodes. It is concatenated together with all its sibling text nodes, and embedded objects between the text nodes are exposed as the unicode embedded object character <c>\xfffc</c>. One reason for this is that there are fewer nodes to pass across process, and that improves performance.</para>
8+
<para><seealso href="https://developer.mozilla.org/en-US/docs/Web/Accessibility/Architecture"> <em>See also on MDN</em> </seealso></para>
9+
</remarks>
10+
</AccessibilityArchitecture>
11+
</docs>

‎CSharpToJavaScript/Utils/Docs/AccessibilityAria/AccessibilityAria.generated.xml‎

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
<docs>
2+
<AccessibilityARIA>
3+
<summary>
4+
It supplements HTML so that interactions and widgets commonly used in applications can be passed to assistive technologies when there is not otherwise a mechanism. For example, ARIA enables accessible JavaScript widgets, form hints and error messages, live content updates, and more.
5+
</summary>
6+
<remarks>
7+
<blockquote class="WARNING"><h5>WARNING</h5><para><strong>Warning:</strong> Many of these widgets are fully supported in modern browsers. <strong>Developers should prefer using the correct semantic HTML element over using ARIA</strong>, if such an element exists. For instance, native elements have built-in <see href="https://developer.mozilla.org/en-US/docs/Web/Accessibility/Keyboard-navigable_JavaScript_widgets">keyboard accessibility</see>, roles and states. However, if you choose to use ARIA, you are responsible for mimicking the equivalent browser behavior in script.</para></blockquote><para><see href="https://www.w3.org/TR/using-aria/#rule1">The first rule of ARIA</see> use is &amp;quot;If you can use a native HTML element or attribute with the semantics and behavior you require already built in, instead of re-purposing an element and adding an ARIA role, state or property to make it accessible, then do so.&amp;quot;</para><blockquote class="NOTE"><h5>NOTE</h5><para><strong>Note:</strong> There is a saying &amp;quot;No ARIA is better than bad ARIA.&amp;quot; In <see href="https://webaim.org/projects/million/#aria">WebAim&amp;apos;s survey of over one million home pages</see>, they found that Home pages with ARIA present averaged 41% more detected errors than those without ARIA. While ARIA is designed to make web pages more accessible, if used incorrectly, it can do more harm than good.</para></blockquote><para>Here&amp;apos;s the markup for a progress bar widget:</para><para>This progress bar is built using a <see href="https://developer.mozilla.org/en-US/docs/Web/HTML/Element/div">div</see>, which has no meaning. We include ARIA roles and properties to add meaning. In this example, the <see href="https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/progressbar_role"><c>role=&amp;quot;progressbar&amp;quot;</c></see> attribute informs the browser that this element is actually a JavaScript-powered progress bar widget. The <see href="https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Attributes/aria-valuemin"><c>aria-valuemin</c></see> and <see href="https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Attributes/aria-valuemax"><c>aria-valuemax</c></see> attributes specify the minimum and maximum values for the progress bar, and the <see href="https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Attributes/aria-valuenow"><c>aria-valuenow</c></see> describes the current state of it and therefore must be kept updated with JavaScript.</para><para>Along with placing them directly in the markup, ARIA attributes can be added to the element and updated dynamically using JavaScript code like this:</para><para>All content that is available to non-assistive technology users must be made available to assistive technologies. Similarly, no features should be included targeting assistive technology users that aren&amp;apos;t also accessible to those not using assistive technologies. The above progressbar needs to be styled to make it look like a progressbar.</para><para>It would have been much simpler to use the native <see href="https://developer.mozilla.org/en-US/docs/Web/HTML/Element/'progress'">'progress'</see> element instead:</para><blockquote class="NOTE"><h5>NOTE</h5><para><strong>Note:</strong> The <c>min</c> attribute is not allowed for the <see href="https://developer.mozilla.org/en-US/docs/Web/HTML/Element/'progress'">'progress'</see> element; its minimum value is always <c>0</c>.</para></blockquote><blockquote class="NOTE"><h5>NOTE</h5><para><strong>Note:</strong> HTML landmark elements (<see href="https://developer.mozilla.org/en-US/docs/Web/HTML/Element/main">main</see>, <see href="https://developer.mozilla.org/en-US/docs/Web/HTML/Element/header">header</see>, <see href="https://developer.mozilla.org/en-US/docs/Web/HTML/Element/nav">nav</see>, etc.) have built-in implicit ARIA roles, so there is no need to duplicate them.</para></blockquote>
8+
<para><seealso href="https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA"> <em>See also on MDN</em> </seealso></para>
9+
</remarks>
10+
</AccessibilityARIA>
11+
</docs>

‎CSharpToJavaScript/Utils/Docs/AccessibilityAriaAnnotations/AccessibilityAriaAnnotations.generated.xml‎

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
<docs>
2+
<AccessibilityARIAAnnotations>
3+
<summary>
4+
Below we&amp;apos;ll introduce the new features associated with ARIA annotations, and have a look at some code examples that show them in action.
5+
</summary>
6+
<remarks>
7+
<blockquote class="NOTE"><h5>NOTE</h5><para><strong>Note:</strong> You can find all the examples discussed in this article in a demo file at <see href="https://mdn.github.io/html-examples/aria-annotations/">aria-annotations</see>.</para></blockquote>
8+
<para><seealso href="https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Annotations"> <em>See also on MDN</em> </seealso></para>
9+
</remarks>
10+
</AccessibilityARIAAnnotations>
11+
</docs>

‎CSharpToJavaScript/Utils/Docs/AccessibilityAriaAttributes/AccessibilityAriaAttributes.generated.xml‎

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
<docs>
2+
<AccessibilityARIAAttributes>
3+
<summary>
4+
&amp;lt;abbr&amp;gt;ARIA&amp;lt;/abbr&amp;gt; attributes enable modifying an element&amp;apos;s states and properties as defined in the accessibility tree.
5+
</summary>
6+
<remarks>
7+
<blockquote class="NOTE"><h5>NOTE</h5><para><strong>Note:</strong> ARIA only modifies the accessibility tree, modifying how assistive technology presents the content to your users. ARIA doesn&amp;apos;t change anything about an element&amp;apos;s function or behavior. When not using semantic HTML elements for their intended purpose and default functionality, you must use JavaScript to manage behavior, focus, and ARIA states.</para></blockquote>
8+
<para>-<see href="https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/ARIA_Techniques">Using ARIA: roles, states, and properties</see><br/>-<see href="https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Attributes"><strong>&amp;lt;abbr&amp;gt;</strong><strong>WAI-ARIA</strong><strong>&amp;lt;/abbr&amp;gt;</strong><strong> attributes</strong></see>ListSubpagesForSidebar("/en-US/docs/Web/Accessibility/ARIA/Attributes")<br/></para>
9+
<para><seealso href="https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Attributes"> <em>See also on MDN</em> </seealso></para>
10+
</remarks>
11+
</AccessibilityARIAAttributes>
12+
</docs>

‎CSharpToJavaScript/Utils/Docs/AccessibilityAriaAttributesAria-activedescendant/AccessibilityAriaAttributesAria-activedescendant.generated.xml‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
<docs>
2+
<AccessibilityARIAAttributesAria-activedescendant>
3+
<summary>
4+
The <c>aria-activedescendant</c> attribute identifies the currently active element when focus is on a <see href="https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/composite_role"><c>composite</c></see> widget, <see href="https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/combobox_role"><c>combobox</c></see>, <see href="https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/textbox_role"><c>textbox</c></see>, <see href="https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/group_role"><c>group</c></see>, or <see href="https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/application_role"><c>application</c></see>.
5+
</summary>
6+
<remarks>
7+
<para><seealso href="https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Attributes/aria-activedescendant"> <em>See also on MDN</em> </seealso></para>
8+
</remarks>
9+
</AccessibilityARIAAttributesAria-activedescendant>
10+
</docs>

0 commit comments

Comments
 (0)