Giter Site home page Giter Site logo

customer-success-samples's People

Contributors

brminnick avatar colbylwilliams avatar conceptdev avatar dependabot[bot] avatar glennwester avatar ianleatherbury avatar jon-davis-xamarin avatar michael-watson avatar patridge avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

customer-success-samples's Issues

[XF] - {1.4.1} - Corpus Christi Independent School District (CCISD) - 28088/[Android/iOS] WebView does not refill/center after rotation

Account Name: Corpus Christi Independent School District (CCISD)
Customer Name: William Shelton
Contract Value: $3,996.00

Bug Frequency (Approx): 100%
Bug Age (Approx): 1.5 weeks

Bug Link: https://bugzilla.xamarin.com/show_bug.cgi?id=28088

Steps to Reproduce:

  1. Download linked test case
  2. Deploy to simulator or device
  3. Rotate device a few times

Observed Result
the view only fills to the point which was filled at its original creation, so
a rotation makes it less filled. This is causing the html to not center
properly

Expected Result
The fill and expand property will allow the webview to always take up the
entire view


Fixed build (in Master): storage location link
Fixed build (in release branch): storage location link
Fixed build (released to Stable): storage location link
CDN uploaded version for Customer (if applicable): build link

[XF] - {1.2.3} - Microsoft - Bug 27374 - Label inside ScrollView does not render correctly on iPhone

Account Name: Microsoft
Customer Name: XXXXXXX
Contract Value: $200k

Bug Frequency (Approx): XX%
Bug Age (Approx): X Days/Weeks/Months

Bug Link: https://bugzilla.xamarin.com/show_bug.cgi?id=27374

Steps to Reproduce:

  1. Step 1
  2. Step 2
  3. Step 3

Observed Result
Expected Result

Any additional details/notes.


Fixed build (in Master): storage location link
Fixed build (in release branch): storage location link
Fixed build (released to Stable): storage location link
CDN uploaded version for Customer (if applicable): build link

[XF] - {1.2.3.6257} - Windows Phone loses styles when adding a ListView to StackLayout

Account Name: Dow Jones
Customer Name: Dustin Dittmer [email protected]
Contract Value: $11,000

Bug Frequency (Approx): XX%
Bug Age (Approx): 23 days (November 12, 2014)

Bug Link: https://bugzilla.xamarin.com/show_bug.cgi?id=24476

Steps to Reproduce:

  1. Reproduction posted as first comment in bug by Jon Douglas

http://www.screencast.com/t/iM4mtC1A2n
which makes it go from this (left) to this (right).

Any additional details/notes.


Fixed build (in Master): storage location link
Fixed build (in release branch): storage location link
Fixed build (released to Stable): storage location link
CDN uploaded version for Customer (if applicable): build link

[XF] - {1.3.3} - Huge Lawn Software - 26696/[Android] Button text alignment changes on Samsung Galaxy S2

Account Name: Huge Lawn Software - Miracle Apps
Customer Name: Mikkel Jensen
Contract Value: $7,192.80

Bug Frequency (Approx): 100%
Bug Age (Approx): 2 weeks

Bug Link: https://bugzilla.xamarin.com/show_bug.cgi?id=26696

Steps to Reproduce:

  1. Run the test case attached to the bug report on a Samsung Galaxy S2.

To a first approximation, the test case is a simple Xamarin.Forms app that contains a Button alongside several Labels within a Grid within a Grid (2 nested Grids).

Observed Result
The "LOG IND" button text is left-aligned.

Expected Result
The "LOG IND" button text is center-aligned. (On most Android devices this is the result.)


Fixed build (in Master): storage location link
Fixed build (in release branch): storage location link
Fixed build (released to Stable): storage location link
CDN uploaded version for Customer (if applicable): build link

[Forms] - {1.4.0} - PSEA - Bug 28366 - [Forms][iOS] Rendering error on ViewCell startup. Navigating off page and going back fixes height property

Account Name: PSEA
Customer Name: Andrew McCormack
Contract Value: $3,798

Bug Frequency (Approx): 100%
Bug Age (Approx): 1 Days

Bug Link: https://bugzilla.xamarin.com/show_bug.cgi?id=28366

Steps to Reproduce:

  1. Download sample app
  2. Run on iOS device or simulator
  3. Press on of the options
  4. Press 'back' button

Observed Result:
Initial rendering for ViewCell does not expand height-wise
Expected Result:
Initial rendering for ViewCell fills and expands for the content.

[XF] - 1.4.1 - BlueTube - Bug 29210 - Xamarin Android failing to render ViewCell for list view in 1.4.1.6347

Account Name: BlueTube
Customer Name: XXXXXXX
Contract Value: $46k

Bug Frequency (Approx): XX%
Bug Age (Approx): X Days/Weeks/Months

Bug Link: https://bugzilla.xamarin.com/show_bug.cgi?id=29210

Steps to Reproduce:

  1. Step 1
  2. Step 2
  3. Step 3

Observed Result
Expected Result

Any additional details/notes.


Fixed build (in Master): storage location link
Fixed build (in release branch): storage location link
Fixed build (released to Stable): storage location link
CDN uploaded version for Customer (if applicable): build link

/* TEMPLATE CARD */ [Product] - {Version} - Customer - Bug Number/Description

Account Name: XXXXXXX
Customer Name: XXXXXXX
Contract Value: XXXXXXX

Bug Frequency (Approx): XX%
Bug Age (Approx): X Days/Weeks/Months

Bug Link: hyperlink to bug

Steps to Reproduce:

  1. Step 1
  2. Step 2
  3. Step 3

Observed Result
Expected Result

Any additional details/notes.


Fixed build (in Master): storage location link
Fixed build (in release branch): storage location link
Fixed build (released to Stable): storage location link
CDN uploaded version for Customer (if applicable): build link

[XF] - {1.4.1} - Deutsche Post - 27649/[Android] Changing the BackgroundColor of a Button many times results in a OOM exception

Account Name: Deutsche Post
Customer Name: Sebastian Span
Contract Value: TBD (large potential, according to J Frederick)

Bug Frequency (Approx): 100%
Bug Age (Approx): 1 month

Bug Link: https://bugzilla.xamarin.com/show_bug.cgi?id=27649

Steps to Reproduce:

  1. Create a forms app with 2 pages, each containing about a dozen buttons in a StackLayout.
  2. Set the NavigatedTo() override to randomize the background colors of all the buttons.
  3. Switch back and forth between the 2 pages many times.

Observed Result
Eventually the app throws an out of memory exception.

Expected Result
Ideally, the memory use of the app should plateau at some moderate level.

Additional information
The problem might be easier to reproduce on some devices than others. The customer saw the problem on a Moto G, Android 4.4.


Fixed build (in Master): storage location link
Fixed build (in release branch): storage location link
Fixed build (released to Stable): storage location link
CDN uploaded version for Customer (if applicable): build link

[Forms] - {1.4.1} - PSEA - Bug 28169 - [iOS] Background color does not maintain in master once detail page is viewed

Account Name: PSEA
Customer Name: Andrew McCormack
Contract Value: $3,798

Bug Frequency (Approx): 100%
Bug Age (Approx): 6 Days

Bug Link: https://bugzilla.xamarin.com/show_bug.cgi?id=28169

Steps to Reproduce:

  1. Download linked app [must be done on Windows]
  2. Deploy to iOS Simulator
  3. Open the master page for the view
  4. Select an item

Expected Results:
The item quickly highlights white when you select it, it should still be white
when you return to the master page

Actual Results:
It turns back to black (the background color of the view)

[XF] - {1.4.2} - Studio 46 - [Android] 29184/ListView group header text is initially white, but refreshes to blue

Account Name: Studio 46
Customer Name: Taylor Lafrinere
Contract Value: $1,998.00

Bug Frequency (Approx): 100%
Bug Age (Approx): 4 days

Bug Link: https://bugzilla.xamarin.com/show_bug.cgi?id=29184

Steps to Reproduce:

  1. Create a Xamarin.Forms app that displays a ListView with IsGroupingEnabled = true and with GroupDisplayBinding set so that the ListView shows group header text.
  2. Launch the app on an Android device or emulator.
  3. Scroll the list view so that 1 new group header text appears on screen. (Or
    scroll 1 of the initial group headers off screen, and then scroll it back
    on screen.)

Observed Result

  • When the app first loads, the on-screen group header text is white while
    the other list items are blue.
  • After step 3, the group header text that was moved from off-screen to
    on-screen is blue rather than white.

Expected Result

I'm not sure if the intended behavior is that the group header text
should always be blue (which would mean the initial state when the app loads
is incorrect), or if the group header text should always be white (which
would mean the state after scrolling the list view is incorrect).


Fixed build (in Master): storage location link
Fixed build (in release branch): storage location link
Fixed build (released to Stable): storage location link
CDN uploaded version for Customer (if applicable): build link

[XF] - {1.2.3.6257} - Adding listview to stacklayout causes text cutoff in Android

Account Name: Dow Jones
Customer Name: Dustin Dittmer [email protected]
Contract Value: $11,000

Bug Frequency (Approx): XX%
Bug Age (Approx): 16days (November 18th, 2014)

Bug Link: https://bugzilla.xamarin.com/show_bug.cgi?id=24628

Steps to Reproduce:

  1. Reproduction first comment on bug

Observed Result
Expected Result

Any additional details/notes.


Fixed build (in Master): storage location link
Fixed build (in release branch): storage location link
Fixed build (released to Stable): storage location link
CDN uploaded version for Customer (if applicable): build link

[XF] - {1.3.3} - KSI & Intelligent InSites - 26664/[Android] MasterBehavior.Split Not Working on Device

Account Name: KSI, LTD and Intelligent InSites
Customer Name: Kirk Kanak & Dan DeBilt
Contract Value: $1,998.00 & $498.00

Bug Frequency (Approx): 100%
Bug Age (Approx): 1 week

Bug Link: https://bugzilla.xamarin.com/show_bug.cgi?id=26664

Steps to Reproduce:

  1. Create a Xamarin.Forms app that displays a MasterDetail page.
  2. Ensure that MasterBehavior is set to MasterBehavior.Split for the page.
  3. Run the app on a Nexus 7 device.

Observed Result
The Master page is rendered as a flyout menu.

Expected Result
The Master and Details pages should always be shown on the screen next to each other (since the Nexus 7 has a sufficiently wide screen).


Fixed build (in Master): storage location link
Fixed build (in release branch): storage location link
Fixed build (released to Stable): storage location link
CDN uploaded version for Customer (if applicable): build link

[XF] - {1.2.3} - Customer - Bug 27270 - Add GeneratedCodeAttribute to generated partial classes

Account Name: Microsoft
Customer Name: XXXXXXX
Contract Value: $200k

Bug Frequency (Approx): XX%
Bug Age (Approx): X Days/Weeks/Months

Bug Link: hyperlink to bug

Steps to Reproduce:

  1. Step 1
  2. Step 2
  3. Step 3

Observed Result
Expected Result

Any additional details/notes.


Fixed build (in Master): storage location link
Fixed build (in release branch): storage location link
Fixed build (released to Stable): storage location link
CDN uploaded version for Customer (if applicable): build link

[XF] - {1.4.3} - Microsoft - Bug 29501 - [Windows] "The name 'InitializeComponent' does not exist in the current context" error when building Windows app

Account Name: Microsoft
Customer Name: XXXXXXX
Contract Value: $100k

Bug Frequency (Approx): XX%
Bug Age (Approx): X Days/Weeks/Months

Bug Link: https://bugzilla.xamarin.com/show_bug.cgi?id=29501

Steps to Reproduce:

  1. Step 1
  2. Step 2
  3. Step 3

Observed Result
Expected Result

Any additional details/notes.


Fixed build (in Master): storage location link
Fixed build (in release branch): storage location link
Fixed build (released to Stable): storage location link
CDN uploaded version for Customer (if applicable): build link

[XF] - {1.3.4} - McKesson - 26895/Toggling IsVisible property off and on repeatedly sometimes causes elements not to render

Account Name: McKesson
Customer Name: Dough Stephens
Contract Value:

Bug Frequency (Approx): 100%
Bug Age (Approx): 1 week

Bug Link: https://bugzilla.xamarin.com/show_bug.cgi?id=26895

Steps to Reproduce:

  1. Run the latest test case attached to the bug report (comment 6).
  2. Set the "How many toggles" field to 1.
  3. Tap the "Toggle IsVisible x number of toggles" repeatedly. (The problem usually appears within the first 30-40 taps of the button.)

As an example of the layout hierarchy in the test case, the ImageButton that gets toggled to be visible / not visible has the following position in the hierarchy:
RelativeLayout -> Frame -> Grid -> ImageButton

Observed Result
The IsVisible properties for the "Patient Intake" ImageButton, the "Patient Intake" Button, and the "How many toggles" are toggled on and off during step 3. Eventually one or more of those elements fails to render when IsVisible is switched to true. The element that fails to render still causes the correct adjustments in the spacings of the layout, but it is not drawn on the screen.

Expected Result
All the elements should appear whenever IsVisible is set back to true.

The problem was partially addressed in 1.3.4, and Jason has replied to the latest updates from the customer to mention that he'll continue to investigate the remaining issues.


Fixed build (in Master): storage location link
Fixed build (in release branch): storage location link
Fixed build (released to Stable): storage location link
CDN uploaded version for Customer (if applicable): build link

[XF] - {1.4.1} - Paylocity - 28556/[All Platforms] Style triggers do not operate correctly when object is disabled initially

Account Name: Paylocity
Customer Name: Paul Patarinski
Contract Value: $37,000.00

Bug Frequency (Approx): 100%
Bug Age (Approx): 1 week

Bug Link: https://bugzilla.xamarin.com/show_bug.cgi?id=28556

Steps to Reproduce:

  1. Open test case
  2. Deploy to iOS or Android Emulator
  3. Tap on "TriggerStyles" on launch page
  4. Notice the 2nd child which is purple (indicating disabled)
  5. Click the "Toggle Enabled" button

Observed Result

The second Entry labeled "Sample Text" should turn green in accordance with the Style.Trigger for the "Enabled" status. The other entries should turn purple to match the "Disabled" status.

Expected Result
The second Entry labeled "Sample Text" turns white, ignoring the Style.Trigger

Additional notes:

I added a "partial workaround" on the bug report: disable the second Entry element later in the page rendering process, for example during the LayoutChildren() override. I believe Support + Success are getting in touch with Paylocity to see if that workaround will suffice for them for right now.


Fixed build (in Master): storage location link
Fixed build (in release branch): storage location link
Fixed build (released to Stable): storage location link
CDN uploaded version for Customer (if applicable): build link

/* TEMPLATE CARD */ [Product] - {Version} - Customer - Bug Number/Description

Account Name: XXXXXXX
Customer Name: XXXXXXX
Contract Value: XXXXXXX

Bug Frequency (Approx): XX%
Bug Age (Approx): X Days/Weeks/Months

Bug Link: hyperlink to bug

Steps to Reproduce:

  1. Step 1
  2. Step 2
  3. Step 3

Observed Result
Expected Result

Any additional details/notes.


Fixed build (in Master): storage location link
Fixed build (in release branch): storage location link
Fixed build (released to Stable): storage location link
CDN uploaded version for Customer (if applicable): build link

iOS version doesn't play video

App Transport Security has blocked a cleartext HTTP (http://) resource load since it is insecure. Temporary exceptions can be configured via your app's Info.plist file.

[XF] - {1.4.1} -Pariveda - Bug 29210 - Xamarin Android failing to render ViewCell for list view in 1.4.1.6347

Account Name: Pariveda Solutions
Customer Name: Compass Healthcare
Contract Value: $46k

Bug Frequency (Approx): XX%
Bug Age (Approx): X Days/Weeks/Months

Bug Link: https://bugzilla.xamarin.com/show_bug.cgi?id=29210

Steps to Reproduce:

  1. Step 1
  2. Step 2
  3. Step 3

Observed Result
Expected Result

Any additional details/notes.


Fixed build (in Master): storage location link
Fixed build (in release branch): storage location link
Fixed build (released to Stable): storage location link
CDN uploaded version for Customer (if applicable): build link

[Forms] - {1.4.0} - PSEA - Bug 28312 - When Master page is open, on rotating the device it does not update the rendering

Account Name: PSEA
Customer Name: Andrew McCormack
Contract Value: $3,798

Bug Frequency (Approx): 100%
Bug Age (Approx): 2 Days

Bug Link: https://bugzilla.xamarin.com/show_bug.cgi?id=28312

Steps to Reproduce:

  1. go from portrait to landscape with the Master opened, the master gets cut
    off and need to reopen it in landscape to view.

Observed Result
Master gets cut off
Expected Result
Master resizes for new screen size

[XF] - {1.4.1} - Deutsche Post - 27642/[Windows Phone] Adding a ScrollView control to a ContentView, removing it and re-adding it causes System.ArgumentException in ystem.Windows.Controls.ContentControl.set_Content()

Account Name: Deutsche Post
Customer Name: Sebastian Span
Contract Value: TBD (large potential, according to J Frederick)

Bug Frequency (Approx): 100%
Bug Age (Approx): 1 month

Bug Link: https://bugzilla.xamarin.com/show_bug.cgi?id=27642

Steps to Reproduce:

  1. Create a ScrollView and store it in an instance variable, like:

    private ScrollView scrollView = new ScrollView {
        Content = new StackLayout {
            Children = {
                new Label { Text = "Hello World" } } } };
    
  2. After the app has loaded, add the view to the ContentPage, remove it, and re-add it (for example, use a button click to trigger this sequence of actions).

(The bug report contains a self-contained test project that does this.)

Observed Result

System.ArgumentException was unhandled by user code
  HResult=-2147024809
  Message=Value does not fall within the expected range.
  Source=System.Windows
  StackTrace:
       at MS.Internal.XcpImports.CheckHResult(UInt32 hr)
       at MS.Internal.XcpImports.SetValue(IManagedPeerBase obj, DependencyProperty property, DependencyObject doh)
       at MS.Internal.XcpImports.SetValue(IManagedPeerBase doh, DependencyProperty property, Object obj)
       at System.Windows.DependencyObject.SetObjectValueToCore(DependencyProperty dp, Object value)
       at System.Windows.DependencyObject.SetEffectiveValue(DependencyProperty property, EffectiveValueEntry& newEntry, Object newValue)
       at System.Windows.DependencyObject.UpdateEffectiveValue(DependencyProperty property, EffectiveValueEntry oldEntry, EffectiveValueEntry& newEntry, ValueOperation operation)
       at System.Windows.DependencyObject.SetValueInternal(DependencyProperty dp, Object value, Boolean allowReadOnlySet)
       at System.Windows.Controls.ContentControl.set_Content(Object value)
       at Xamarin.Forms.Platform.WinPhone.ScrollViewRenderer.LoadContent()
       at Xamarin.Forms.Platform.WinPhone.ScrollViewRenderer.OnElementChanged(ElementChangedEventArgs`1 e)

Expected Result
No errors. (The same app succeeds on Android.)


Fixed build (in Master): storage location link
Fixed build (in release branch): storage location link
Fixed build (released to Stable): storage location link
CDN uploaded version for Customer (if applicable): build link

[Class Libraries] - {3.12} – Computer Services, Inc. - 29660/Polymorphic Json Deserialization Error

Account Name: Computer Services, Inc.
Customer Name: Carlo Wahlstedt
Contract Value: $4,000

Bug Frequency (Approx): 100%
Bug Age (Approx): 2 Months

Bug Link: https://bugzilla.xamarin.com/show_bug.cgi?id=29660

Steps to Reproduce:

  1. Download Polymorphic Json Sample from Bugzilla
  2. Run sample

Observed Result
Same stack trace as previous bug fix (Bug 3811) but the paths are different.

Now:
/Developer/MonoTouch/Source/monotouch/_build
//Library/Frameworks/Xamarin.iOS.framework/Versions/git/src/mono/mcs/class/System.ServiceModel.Web/System.Runtime.Serialization.Json/JsonSerializationReader.cs:190

Expected Result

Deseralized json object

Any additional details/notes.

May be a duplicate of Bug 26998. This happened after the follow bug was
resolved fixed in Bug 3811


Fixed build (in Master): storage location link
Fixed build (in release branch): storage location link
Fixed build (released to Stable): storage location link
CDN uploaded version for Customer (if applicable): build link

Create forms sample similar to iOS settings

I’d like to have a seletion control that behaves like under Android and iOS:
It displays a caption/text and the selected value with an accessory type “DisclosureIndictator” like illustrated in the iOS Settings app for the app Safari or for the :
image
When clicking on the control, a page with a list of items is shown where one item can be selected like illustrated above:
image

[XF] - {1.4.1} - Lotpath - 27627/[iOS] Read only property within a ScrollView loses "read only" status after quick back and forth scrolling

Account Name: Lotpath
Customer Name: Greg Fiske
Contract Value: $1,998.00

Bug Frequency (Approx): 80%
Bug Age (Approx): 2 weeks

Bug Link: https://bugzilla.xamarin.com/show_bug.cgi?id=27627

Steps to Reproduce:

  1. Open the test case from https://bugzilla.xamarin.com/show_bug.cgi?id=27627#c0
  2. Deploy to iOS Simulator
  3. Log in with default username and password
  4. Click on Niche Vineyards
  5. Click on the first item in the list to open the detail view
  6. Notice some fields are read only
  7. Scroll down and back up quickly
  8. Repeat step 7 a few times if needed

Observed Result
Some of the read-only fields become writable. For example, I have observed the problem fairly consistently with the "Plan Name" and "Commodity" fields at the very top of the ScrollView.

Expected Result
The read-only fields remain read-only after any amount of scrolling.


Fixed build (in Master): storage location link
Fixed build (in release branch): storage location link
Fixed build (released to Stable): storage location link
CDN uploaded version for Customer (if applicable): build link

[XF] - {1.3.4} - Verso - Managed to native SIGSEGV in FormsTemplateiOS

Account Name: Verso Solutions Sàrl
Customer Name: Adrien Teccani
Contract Value:

Bug Frequency (Approx): 100%
Bug Age (Approx): 1 week

Bug Link: https://bugzilla.xamarin.com/show_bug.cgi?id=27017

Description

The following app uses Xamarin.Forms Shared Project, and fails when deploying
to iOS. It does not fail for Android or WinPhone.

Test Case

https://www.dropbox.com/s/8qrxps0medepo51/bity.zip?dl=0


Fixed build (in Master): storage location link
Fixed build (in release branch): storage location link
Fixed build (released to Stable): storage location link
CDN uploaded version for Customer (if applicable): build link

[XF] - {1.2.3} - Microsoft - Bug 27267 - Allow assembly to be inferred rather than required

Account Name: Microsoft
Customer Name: XXXXXXX
Contract Value: $200k

Bug Frequency (Approx): XX%
Bug Age (Approx): X Days/Weeks/Months

Bug Link: https://bugzilla.xamarin.com/show_bug.cgi?id=27267

Steps to Reproduce:

  1. Step 1
  2. Step 2
  3. Step 3

Observed Result
Expected Result

Any additional details/notes.


Fixed build (in Master): storage location link
Fixed build (in release branch): storage location link
Fixed build (released to Stable): storage location link
CDN uploaded version for Customer (if applicable): build link

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.