Using https for embedded fiddles
Official announcement from jsfiddle: https://twitter.com/jsfiddle/status/565041134435852289
Stefan Dombrowski committed
Feb 18, 2015 at 23:07 UTC
8ba3ba49d2644b1d6267ecd300d6b9a37520c64b
5 files changed
+10
-14
docs/_posts/2013-09-24-community-roundup-8.md
+1
-1
@@ -66,4 +66,4 @@ While this is not going to work for all the attributes since they are camelCased
66
67
[Vjeux](http://blog.vjeux.com/) re-implemented the display part of the IRC logger in React. Just 130 lines are needed for a performant infinite scroll with timestamps and color-coded author names.
68
69
-<iframe width="100%" height="300" src="http://jsfiddle.net/vjeux/QL9tz/embedded/" allowfullscreen="allowfullscreen" frameborder="0"></iframe>
69
+<iframe width="100%" height="300" src="https://jsfiddle.net/vjeux/QL9tz/embedded/" allowfullscreen="allowfullscreen" frameborder="0"></iframe>
docs/_posts/2013-11-05-thinking-in-react.md
+3
-3
@@ -56,7 +56,7 @@ Now that we've identified the components in our mock, let's arrange them into a
56
57
## Step 2: Build a static version in React
58
59
-<iframe width="100%" height="300" src="http://jsfiddle.net/6wQMG/embedded/" allowfullscreen="allowfullscreen" frameborder="0"></iframe>
59
+<iframe width="100%" height="300" src="https://jsfiddle.net/6wQMG/embedded/" allowfullscreen="allowfullscreen" frameborder="0"></iframe>
60
61
Now that you have your component hierarchy it's time to start implementing your app. The easiest way is to build a version that takes your data model and renders the UI but has no interactivity. It's easiest to decouple these processes because building a static version requires a lot of typing and no thinking, and adding interactivity requires a lot of thinking and not a lot of typing. We'll see why.
62
@@ -100,7 +100,7 @@ So finally, our state is:
100
101
## Step 4: Identify where your state should live
102
103
-<iframe width="100%" height="300" src="http://jsfiddle.net/QvHnx/embedded/" allowfullscreen="allowfullscreen" frameborder="0"></iframe>
103
+<iframe width="100%" height="300" src="https://jsfiddle.net/QvHnx/embedded/" allowfullscreen="allowfullscreen" frameborder="0"></iframe>
104
105
OK, so we've identified what the minimal set of app state is. Next we need to identify which component mutates, or *owns*, this state.
106
@@ -125,7 +125,7 @@ You can start seeing how your application will behave: set `filterText` to `"bal
125
126
## Step 5: Add inverse data flow
127
128
-<iframe width="100%" height="300" src="http://jsfiddle.net/3Vs3Q/embedded/" allowfullscreen="allowfullscreen" frameborder="0"></iframe>
128
+<iframe width="100%" height="300" src="https://jsfiddle.net/3Vs3Q/embedded/" allowfullscreen="allowfullscreen" frameborder="0"></iframe>
129
130
So far we've built an app that renders correctly as a function of props and state flowing down the hierarchy. Now it's time to support data flowing the other way: the form components deep in the hierarchy need to update the state in `FilterableProductTable`.
131
docs/_posts/2013-12-23-community-roundup-12.md
+1
-1
@@ -63,7 +63,7 @@ React declarative approach is well suited to write games. [Cheng Lou](https://gi
63
64
[Ross Allen](https://twitter.com/ssorallen) implemented [MontageJS](http://montagejs.org/)'s [Reddit tutorial](http://montagejs.org/docs/tutorial-reddit-client-with-montagejs.html) in React. This is a good opportunity to compare the philosophies of the two libraries.
65
66
-<iframe width="100%" height="300" src="http://jsfiddle.net/ssorallen/fEsYt/embedded/result,html,js" allowfullscreen="allowfullscreen" frameborder="0"></iframe>
66
+<iframe width="100%" height="300" src="https://jsfiddle.net/ssorallen/fEsYt/embedded/result,html,js" allowfullscreen="allowfullscreen" frameborder="0"></iframe>
67
68
[View the source on JSFiddle...](http://jsfiddle.net/ssorallen/fEsYt/)
69
docs/_posts/2014-01-06-community-roundup-14.md
+2
-2
@@ -45,7 +45,7 @@ rails s
45
46
[Eldar Djafarov](http://eldar.djafarov.com/) implemented a mixin to link Backbone models to React state and a small abstraction to write two-way binding on-top.
47
48
-<iframe width="100%" height="300" src="http://jsfiddle.net/djkojb/qZf48/13/embedded/" allowfullscreen="allowfullscreen" frameborder="0"></iframe>
48
+<iframe width="100%" height="300" src="https://jsfiddle.net/djkojb/qZf48/13/embedded/" allowfullscreen="allowfullscreen" frameborder="0"></iframe>
49
50
[Check out the blog post...](http://eldar.djafarov.com/2013/11/reactjs-mixing-with-backbone/)
51
@@ -71,7 +71,7 @@ rails s
71
72
[Thomas Aylott](http://subtlegradient.com/) implemented an API that looks like Web Components but using React underneath.
73
74
-<iframe width="100%" height="300" src="http://jsfiddle.net/SubtleGradient/ue2Aa/embedded/html,js,result" allowfullscreen="allowfullscreen" frameborder="0"></iframe>
74
+<iframe width="100%" height="300" src="https://jsfiddle.net/SubtleGradient/ue2Aa/embedded/html,js,result" allowfullscreen="allowfullscreen" frameborder="0"></iframe>
75
76
77
## React vs Angular
docs/docs/thinking-in-react.md
+3
-7
@@ -11,10 +11,6 @@ React is, in my opinion, the premier way to build big, fast Web apps with JavaSc
11
12
One of the many great parts of React is how it makes you think about apps as you build them. In this post I'll walk you through the thought process of building a searchable product data table using React.
13
14
-> Note:
15
->
16
-> If you can't see the embedded code snippets on this page, make sure you're NOT loading this page on `https`.
17
-
14
## Start with a mock
15
16
Imagine that we already have a JSON API and a mock from our designer. Our designer apparently isn't very good because the mock looks like this:
@@ -64,7 +60,7 @@ Now that we've identified the components in our mock, let's arrange them into a
60
61
## Step 2: Build a static version in React
62
67
-<iframe width="100%" height="300" src="http://jsfiddle.net/reactjs/yun1vgqb/embedded/" allowfullscreen="allowfullscreen" frameborder="0"></iframe>
63
+<iframe width="100%" height="300" src="https://jsfiddle.net/reactjs/yun1vgqb/embedded/" allowfullscreen="allowfullscreen" frameborder="0"></iframe>
64
65
Now that you have your component hierarchy it's time to start implementing your app. The easiest way is to build a version that takes your data model and renders the UI but has no interactivity. It's easiest to decouple these processes because building a static version requires a lot of typing and no thinking, and adding interactivity requires a lot of thinking and not a lot of typing. We'll see why.
66
@@ -108,7 +104,7 @@ So finally, our state is:
104
105
## Step 4: Identify where your state should live
106
111
-<iframe width="100%" height="300" src="http://jsfiddle.net/reactjs/zafjbw1e/embedded/" allowfullscreen="allowfullscreen" frameborder="0"></iframe>
107
+<iframe width="100%" height="300" src="https://jsfiddle.net/reactjs/zafjbw1e/embedded/" allowfullscreen="allowfullscreen" frameborder="0"></iframe>
108
109
OK, so we've identified what the minimal set of app state is. Next we need to identify which component mutates, or *owns*, this state.
110
@@ -133,7 +129,7 @@ You can start seeing how your application will behave: set `filterText` to `"bal
129
130
## Step 5: Add inverse data flow
131
136
-<iframe width="100%" height="300" src="http://jsfiddle.net/reactjs/n47gckhr/embedded/" allowfullscreen="allowfullscreen" frameborder="0"></iframe>
132
+<iframe width="100%" height="300" src="https://jsfiddle.net/reactjs/n47gckhr/embedded/" allowfullscreen="allowfullscreen" frameborder="0"></iframe>
133
134
So far we've built an app that renders correctly as a function of props and state flowing down the hierarchy. Now it's time to support data flowing the other way: the form components deep in the hierarchy need to update the state in `FilterableProductTable`.
135