Forums - CSHTML5

I tested the version downloaded on 22 Oct.
the XAML as below:


and the code is below


it reports error when I switched the two tabs in 2 times.
and another bug is when the program starts, the initial view does not show the first tab

Hi and welcome to the forums.

Thanks for reporting this issue. We are going to fix it in the coming weeks (Beta 9.2 or 9.3).

Regards,
JS-Support

Hi,

The issue has been fixed in Beta 10.1, available from:
http://forums.cshtml5.com/viewforum.php?f=6

Thanks.
Regards,
JS-Support

Dear JS-Support,

for your kind information the TabControl is better, but some other bug still exist:

Symptoms:
-Two TabItem get stucked: "two blue line" / like two tabitems selected at the same time:



-Unhandled exception:
"Uncaught NotFoundError: Failed to execute 'removeChild' on 'Node': The node to be removed is not a child of this node."

function INTERNAL_HtmlDomManager_RemoveOptionFromNativeComboBox (optionToRemove, nativeComboBoxDomElement) {
nativeComboBoxDomElement.removeChild(optionToRemove);
};

Please, double check it ! -can you reproduce the bug ?
Really waiting for your solution as actually the only workaround with multiple tabitem to reload the whole page ((

Thanks in advance,
Best Regards,
Péter

Sesztak wrote:for your kind information the TabControl is better, but some other bug still exist:
...
-can you reproduce the bug ?

Hi Péter,

Thanks for your message. The TabControl in the sample Showcase application (under the "Controls" section) appears to work fine, as well as those in our tests. Could you please send me a code snippet to reproduce the issue?

Thanks.

Dear JS-Support,

Do not joke with me !!: if you put only one TextBlock on a TabItem - yes, you are right !: no problem at all,

But: It's clearly written in our previous message:
""Uncaught NotFoundError: Failed to execute 'removeChild' on 'Node': The node to be removed is not a child of this node."

function INTERNAL_HtmlDomManager_RemoveOptionFromNativeComboBox (optionToRemove, nativeComboBoxDomElement) {
nativeComboBoxDomElement.removeChild(optionToRemove);
};"

So, the the the only thing you do should have to do: just put a ComboBox with some data.
(instead of asking me to do the same ! )

Anyway, no problem I did the home work :

XAML:
<Page
x:Class="CSHTML5_removeChildOnNode_BUG.MainPage"
xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
xmlns:local="using:CSHTML5_removeChildOnNode_BUG"
xmlns:d="http://schemas.microsoft.com/expression/blend/2008"
xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006"
mc:Ignorable="d">
<Canvas>
<TabControl>
<TabItem Header="tabItem A">
<ComboBox x:Name="comboBox1" Margin="6,0,0,0" Padding="3" DisplayMemberPath="Name"/>
</TabItem>
<TabItem Header="tabItem B">
<TextBlock Text="Go back to 'tabItem A' and play with 'comboBox1' => Bug arrived ! "/>
</TabItem>
</TabControl>
</Canvas>
</Page>

C#:
using System;
using System.Collections.Generic;
using System.Collections.ObjectModel;
using System.IO;
using System.Linq;
using Windows.UI.Xaml;
using Windows.UI.Xaml.Controls;

namespace CSHTML5_removeChildOnNode_BUG
{
public partial class MainPage : Page
{
public MainPage()
{
this.InitializeComponent();
ObservableCollection<DataSample> _DataSample = new ObservableCollection<DataSample>() {
new DataSample() {Name ="Emil" },
new DataSample() {Name ="Peter" }
};
comboBox1.ItemsSource = _DataSample;
}

class DataSample
{
public string Name { get; set; }
}
}
}

How to reproduce the bug:
1./ First TabItem select some item from combobox,
2./ Select the other tabitem ("tabItem B"),
3./ Go back to first tabitem: you got exception.


I really hope it helps to fix the bug !

please, confirm: can you reproduce the bug ?

Waiting for your kind reply,
Br,
Péter